> ## Documentation Index
> Fetch the complete documentation index at: https://ade-app.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Review proof

> The capture → review → attach lifecycle: owners, review states, and good habits.

Proof is only useful when it's easy to review and tied to the work it supports. A screenshot without an owner is just a file; the same screenshot linked to a PR and chat explains what it proves. The lifecycle is short — capture, review, attach — and every artifact carries an owner and a review state.

## Where proof surfaces

Proof shows up in two places:

* **Chat** — the proof drawer below the composer shows a thumbnail grid for the current session. Captions render in full under each thumbnail; click to preview at full size.
* **Lane and PR review** — linked proof is surfaced alongside lane work and at PR closeout, where reviewers actually look.

## Owners

A single proof can be linked to more than one owner. That link is what makes the artifact useful later, and adding an owner never drops the existing ones — provenance is preserved as evidence flows downstream.

* **Chat session** — the conversation that produced it.
* **Lane** — the worktree the work happened in.
* **Pull request** — where reviewers actually look.
* **Linear issue** — when Linear is connected; attached at closeout.
* **Automation run** — when a dispatched agent or CTO worker captured it.

## Review states

Every artifact moves through a small set of states so reviewers know what's been judged:

| State | Meaning |
| - | - |
| **Pending** | Captured, not reviewed yet (the default). |
| **Accepted** | Good evidence for the claim. |
| **Needs more** | Useful but incomplete — capture again. |
| **Dismissed** | Not relevant to the final result. |
| **Published** | Promoted to a PR comment or Linear issue. |

Accept / request-more / dismiss are first-class controls on each proof in the drawer.

## The lifecycle

**1. Capture**

Capture a screenshot, recording, trace, log, or verification note from the relevant chat or lane.

**2. Review**

Open the proof and decide whether it supports the work — accept, request more, or dismiss.

**3. Attach**

Link accepted proof to the PR, Linear issue, lane, or chat. The same artifact can ride along to several owners at once.

**4. Reference**

Use the proof during review so the result is inspectable, not just asserted.

## Demo videos

A recording an agent makes as proof is meant to read like a product post. While it records:

* The video rests on the part of the screen where things happen, so a small app fills the frame.
* Typing appears one character at a time and plays at normal speed, on every surface (browser, App Control, the desktop drivers, and the simulator).
* The drawn pointer glides to what it hovers and carries a drag to its end, and a key press shows a badge such as "Cmd + K".

None of this changes input when nothing is recording. On the iPhone, a proof video in a chat plays inline; tap to play or pause, or open the full-screen player.

Before posting, `ade proof review <id>` gives the agent a frame sheet of the video and flags problems such as a recording that is too short or has no captions. `ade proof publish --pr <n> --replace <id>` posts the new proof and deletes the earlier ADE proof comments on that PR.

## Good proof habits

* Capture **after** the relevant change is visible, not during the work.
* Write a caption that names the exact state being proven — "checkout succeeds, confirmation visible," not "screenshot 3."
* Keep a set to three to eight captures a reviewer can read in one pass; avoid dumping a screenshot after every click.
* Attach test output or a verification note when the proof is about correctness.
* Dismiss proof that no longer supports the final result, so the record stays honest.

> [!TIP]
>
> For a reviewer, the strongest PR pairs a visual proof with a short verification note: a screenshot of the result plus one line on what was checked and why it passed.

> [card] [Proof overview](https://ade-app.dev/docs/computer-use/overview.md)
>
> What proof is and why it matters.

> [card] [Proof configuration](https://ade-app.dev/docs/computer-use/config.md)
>
> Storage, retention, and troubleshooting.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.