IHVRK evidence: Independent Human Verification Resource Kit
Published by the CAIN-42 developer. This is not an independent audit. IHVRK holds a high-impact agent action until an enrolled human verifier approves that exact action, then lets it run once, with a checkable record of every step.
Check it yourself (about 1 minute, Python 3.8+, nothing to install)
mkdir ihvrk && cd ihvrk
for f in $(curl -fsS https://cainstudio.online/evidence/ihvrk/MANIFEST.json | python3 -c "import json,sys;print(' '.join(json.load(sys.stdin)['files']))") MANIFEST.json verify_ihvrk_evidence.py; do
mkdir -p "$(dirname "$f")"; curl -fsS "https://cainstudio.online/evidence/ihvrk/$f" -o "$f"; done
python3 -I verify_ihvrk_evidence.py
Expected last line: RESULT: PASS (9 checks, 0 failed), exit code 0. Edit any file and run it again: check E1 must fail.
What this bundle records
- Source commit
ef92dfd109e9f83d72662a11126564789785ffec(repository is private), tree clean at generation: True. - Tests: 301 passed, 0 failed, 0 errors, 0 skipped.
- Mutation testing of the security guards: 30/30 killed (a mutation score is not code coverage).
- Z3 proofs of policy invariants I1–I15, TLA+/TLC model checks of the protocol (bounded model), a sample signed ledger and three tampered copies the verifier must reject.
Release gate (developer’s own labels, verbatim)
| Gate | Blocks when | Result |
|---|---|---|
| G1 | forbidden execution state reachable in a required formal model | PASS |
| G2 | required safety invariant fails | PASS |
| G3 | critical authorization or replay test fails | PASS |
| G4 | invalid approval produces a permit | PASS |
| G5 | unresolved solver result grants permission | PASS |
| G6 | protected action executes without a valid action-bound permit | PASS |
| G7 | critical ledger-integrity test fails | PASS |
| G8 | required runtime enforcement control missing | BLOCKED — eBPF LSM not attachable on host (bpf not in active LSM list); user-space map daemon not written |
| G9 | known critical defect lacks a disposition | PASS |
| G10 | artifact cannot be linked to tested source revision | PASS |
| G11 | required evidence missing or unverifiable | PASS |
| G12 | deployment violates a mandatory trust assumption | BLOCKED — not integrated into any live CAIN path (L-INTEG); service keys are SOFTWARE_TEST (L-HSM) |
Full scope: RELEASE_GATE_BLOCKED. Library scope: RELEASE_CANDIDATE_WITH_OPEN_FINDINGS. IHVRK is not integrated into the live CAIN gateway, MCPGate or these sites, and has had no third-party review.
What a PASS does not prove
That these results came from code you can run (the source is private; re-running needs repository access), that the release key or any deployment is trustworthy, or that IHVRK is production-ready.
Files
- KIT_SLOT.json
- MANIFEST.json
- benchmark.json
- docs/
- ebpf_verifier_load.txt
- mutation.json
- sample_ledger/
- test_results.json
- tlc/
- tlc_summary.json
- verify_ihvrk_evidence.py
- z3_proofs.json
Start with docs/auditor/QUICKSTART.md, then docs/LIMITATIONS.md. Also see the Verification Center.