> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-ade-im-seeing-error-messag-eright-58df792e.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Proof Overview

> Proof is ADE's intentional evidence system. Agents capture screenshots, recordings, traces, and logs via the `ade proof` CLI; ADE stores and links them to worker runs, chats, PRs, and Linear issues.

## Overview

Proof is ADE's way of collecting **intentional evidence** during agent work. Workers and chat agents capture screenshots, short recordings, browser traces, verification snapshots, and console logs through the `ade proof` CLI. ADE stores the resulting artifacts, normalizes them, and links them to the worker run, chat session, PR, or Linear issue that produced them.

There is no separate computer-use broker, no backend negotiation, and no per-session policy chip. Agents simply call `ade proof` when they want to leave a trail.

<CardGroup cols={2}>
  <Card title="Intentional Evidence" icon="camera">
    Proof is explicit. Agents decide when a piece of work deserves a screenshot or recording — there is no background recording of every action.
  </Card>

  <Card title="Unified Artifacts" icon="database">
    Every proof is stored with a canonical record: kind, owner, storage path, MIME type, and metadata. The same normalized schema powers worker run artifact tabs, chat session history, and PR attachments.
  </Card>

  <Card title="Single CLI Surface" icon="terminal">
    Agents use `ade proof capture`, `ade proof record`, `ade proof list`, and a few related commands. See the [Setup](/computer-use/setup) page for the full command list.
  </Card>

  <Card title="Routed to Owners" icon="link">
    Proofs are linked to lanes, worker runs, chat sessions, PRs, and Linear issues. Review and publish them from the Worker run Artifacts tab or the chat artifact panel.
  </Card>
</CardGroup>

***

## Proof Kinds

ADE recognizes five proof kinds. All kinds share the same storage, ownership, and routing model — the kind only changes what the CLI captures and what the viewer shows.

| Kind                   | What it is                                                                                  |
| ---------------------- | ------------------------------------------------------------------------------------------- |
| `screenshot`           | A static PNG/JPEG of the current screen or browser viewport                                 |
| `video_recording`      | A short screen recording captured by `ade proof record`                                     |
| `browser_trace`        | A machine-readable record of browser interactions ingested from an external tool            |
| `browser_verification` | An assertion result (did an expected DOM element exist, did the page contain expected text) |
| `console_logs`         | Captured browser or application console output                                              |

Screenshots and short recordings are the most common kinds, because they can be captured directly by `ade proof` without any external dependency.

***

## Where Proofs Show Up

| Context       | Where proofs appear                                                                                     |
| ------------- | ------------------------------------------------------------------------------------------------------- |
| Workers       | The **Artifacts tab** on every worker run detail view lists every proof captured during that worker run |
| Agent Chat    | The session artifact panel surfaces proofs captured inside a chat session                               |
| Pull Requests | Proofs routed to a PR appear in the **Path to Merge** tab as inline attachments                         |
| Linear Issues | Published proofs are posted as attachments on the linked Linear issue                                   |
| Lanes         | Every proof retains a link back to the lane the agent was working in                                    |

Agents attach proofs to owners when they capture them, or later via `ade proof` subcommands. You can also promote a proof from the UI — for example, sending a before/after screenshot from a chat session to a PR with a single click.

***

## Next Steps

<CardGroup cols={3}>
  <Card title="Setup & CLI" icon="terminal" href="/computer-use/setup">
    Install prerequisites and walk through the `ade proof` commands agents use.
  </Card>

  <Card title="Proof Workflow" icon="camera" href="/computer-use/proofs">
    How proofs are owned, reviewed, and published to PRs and Linear issues.
  </Card>

  <Card title="Configuration" icon="sliders" href="/computer-use/config">
    Storage paths, retention, and troubleshooting common capture issues.
  </Card>
</CardGroup>