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

> ## Agent Instructions
> Treat availability labels as authoritative. Do not present planned surfaces as live.
> The product MCP can act on Actual Jobs; the documentation MCP cannot.

# Evidence and Verification

> Why provider claims and execution records do not by themselves prove an Outcome.

**Evidence** is a durable item used to establish execution or physical state: a receipt, photo, telemetry sample, call result, Provider record, User confirmation, or independent inspection.

Evidence is input to **Verification**. It is not automatically proof.

## Verification

Verification evaluates Evidence against a versioned, category-specific policy. The verifier may be automated or human, but it is independent of the same Agent invocation that proposed and executed the consequential action.

Only a successful Verification transaction can create an Outcome and complete a Job. Until then:

* a booking confirms an appointment, not the physical result;
* a payment confirms a money event, not satisfactory work;
* a Provider webhook is an untrusted, deduplicated hint;
* a screenshot or model claim is Evidence, not completion.

## Insufficient Evidence

Actual can request more Evidence or enter Recovery. Recovery preserves prior facts while it reconciles, rebooks, disputes, requests a return visit, or finds another Provider.

<Note>Public Evidence submission and retrieval endpoints are planned.</Note>