Proof workflow

Capture, review, and attach evidence to chats, lanes, PRs, Linear issues, and worker activity.

Proof is only useful when it is easy to review and tied to the work it supports.

Proof kinds

Kind	Typical use
Screenshot	Confirm a UI state or visible result.
Recording	Show a short flow or reproduction.
Browser trace	Preserve structured browser diagnostics from a test tool.
Console logs	Attach useful runtime or browser output.
Verification note	Record what was checked and what passed.

Owners

A proof can be linked to more than one owner:

• Lane.
• Chat session.
• Pull request.
• Linear issue.
• Worker task or worker activity.

That link is what makes the artifact useful later. A screenshot without an owner is just a file; a screenshot linked to a PR and chat explains what it proves.

Review states

State	Meaning
Pending	Not reviewed yet.
Accepted	Good evidence for the claim.
Needs more	Useful but incomplete.
Dismissed	Not relevant.

Basic lifecycle

1. Capture

   Capture a screenshot, recording, trace, log, or verification note.

2. Review

   Open the proof and decide whether it supports the work.

3. Attach

   Link accepted proof to the PR, Linear issue, lane, chat, or worker activity.

4. Reference

   Use the proof during review so the result is inspectable.

Good proof habits

• Capture after the relevant change is visible.
• Give the artifact a plain title.
• Attach test output when the proof is about correctness.
• Prefer one clear screenshot over a long unrelated recording.
• Dismiss proof that no longer supports the final result.