# Independent verification guide (Evolution 14)

You need Python 3.9+ and the `cryptography` package. You do not need CAIN.

```
python3 verify.py release  <release-dir> --policy release_policy.json --expect-commit b6f440bd9eb0e34ece6d1db65701b0edfe964efa
python3 verify.py deployment export.json --trust trust.public.json
python3 verify.py soak soak.jsonl --require-hours 72
```

Statuses: VERIFIED, REJECTED, INCONSISTENT, UNAVAILABLE, INSUFFICIENT_EVIDENCE, OUTCOME_UNKNOWN, BLOCKED.
Exit 0 only for VERIFIED. A producer's summary is compared with the evidence, never used as evidence.

What you can establish: the release bytes match a manifest signed by both policy keys; the provenance names those
bytes and that commit; the deployment's every effect has an ALLOW decision for that exact action, a gate-signed
observation and an inclusion proof in the witnessed log; at least 3 distinct pinned witnesses signed that checkpoint;
the soak records form an unbroken hash chain covering the elapsed time they claim.

What you cannot establish, and why:
- that the commit exists or contains what the SBOM lists (the repository is private; you get hash commitments);
- that the keys you were given are the right ones (check them out of band: DNS TXT, Rekor, a second channel);
- that the soak's clock was honest (records are timestamped by the host that ran it);
- independence: the verifier, the producer and the keys come from the same project and the same person.
