When Bright summarizes a connected app, open the original record before you turn the summary into a decision. A citation proves that a record exists. It does not prove that the agent captured its most decision-relevant state. The facts that change a conclusion are often visible on the record and missing from the synthesis. Open Bright →

​
Why direct verification changes the decision

A connector report inferred that a repository was the primary release candidate. Opening the cited GitHub record added two facts that changed the conclusion: the repository had been archived, and its review checklist showed no ship decision approved. Both facts were visible on the record; neither survived into the synthesis.

​
Source-trace workflow

  1. Open the exact provider link Bright returned.
  2. Verify ownership, visibility, archive state, branch, latest update, and read/write status.
  3. Open the specific cited file or page rather than relying on repository-level context.
  4. Check whether checklist items are completed or merely present.
  5. Compare titles, totals, dates, and statuses with Bright’s summary.
  6. Record mismatches before the result becomes a plan or a document.

​
Reviewing Notion records

For Notion, verify the page breadcrumb, the parent project, the last-edited state, and whether the visible content belongs to the intended project. Do not publish screenshots of private workspace navigation or personal specifications unless the owner approves the disclosure.

​
Good to know

  • A citation proves that a record exists. It does not prove that the agent captured its most decision-relevant state.
  • Hand work to coding agents covers verifying acceptance criteria before and after a handoff.
  • Connect apps covers where connections live and what each one grants.

​
Next step

Learn what a session can see, what a provider permits, and when a tool needs your approval in Context, permissions, and safe operation.