# IHVRK auditor quickstart (about 1 minute)

Inside the published evidence folder (`/evidence/ihvrk/` on the CAIN-42 sites, or `EVIDENCE/ihvrk/` in the auditor
kit), with Python 3.8+ and nothing else installed:

```bash
python3 verify_ihvrk_evidence.py
```

Expected: every line `PASS`, last line `RESULT: PASS (9 checks, 0 failed)`, exit code 0.

What that tells you: the evidence files are the ones listed in MANIFEST.json; the recorded test, Z3, TLC and
mutation results show what the documents claim; a sample ledger and its signed checkpoint verify; and three tampered
copies are rejected. All of it is checked with code that shares nothing with the implementation.

What it does not tell you: that these results came from the code you would run, unless you re-run them yourself
from the source commit in MANIFEST.json (VERIFY_INSTRUCTIONS.md §2, which needs repository access). It also says
nothing about any production deployment, and IHVRK is not deployed in production.