> For the complete documentation index, see [llms.txt](https://dsg-3.gitbook.io/dsg-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dsg-3.gitbook.io/dsg-docs/cinema-proof-agent/runtime-and-integrations/evidence-verification-and-replay.md).

# Evidence, Verification and Replay

How Cinema derives verdicts from raw material, hashes evidence, proves receipts, and keeps replay non-mutating.

Cinema separates caller assertions from verifier judgment.

## Raw material, not caller verdicts

The v1 flow accepts plans, observed actions, constraints, artifacts, and execution facts. Cinema derives its own alignment, execution, evidence, replay, and authorization results.

Requests that try to supply DSG-computed verdict fields as if they were facts are rejected before reaching the verification engine.

## Evidence hashing

When evidence content is supplied, Cinema hashes the content itself. A declared digest that disagrees with the actual bytes is rejected.

Hash-only evidence can be recorded, but it does not satisfy a content-required proof step by itself.

## Replay

Replay is a comparison, not a new execution.

```
recorded output digest
        +
content-verified evidence
        ↓
recompute digest
        ↓
match / mismatch
```

No matching submitted content means there is no replay proof.

## Exact verification

Post-execution verification can return:

* `BLOCK` — authorization or block-severity boundary failure;
* `REVIEW` — incomplete execution, review finding, replay mismatch, or incomplete evidence;
* `ALLOW` — none of those conditions remain.

This is different from pre-execution `WAITING_PERMISSION`.

Where the contract requires exact Z3 verification, the verifier must produce the expected witness. If the verifier is unavailable, the request fails and no verified receipt is created.

## Receipt integrity

A proof receipt commits to hashes of the approved plan, observed action trace, alignment, constraints, evidence, and replay material. Receipt retrieval recomputes the receipt hash rather than trusting a stored display value.
