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

Release gate (developer’s own labels, verbatim)

GateBlocks whenResult
G1forbidden execution state reachable in a required formal modelPASS
G2required safety invariant failsPASS
G3critical authorization or replay test failsPASS
G4invalid approval produces a permitPASS
G5unresolved solver result grants permissionPASS
G6protected action executes without a valid action-bound permitPASS
G7critical ledger-integrity test failsPASS
G8required runtime enforcement control missingBLOCKED — eBPF LSM not attachable on host (bpf not in active LSM list); user-space map daemon not written
G9known critical defect lacks a dispositionPASS
G10artifact cannot be linked to tested source revisionPASS
G11required evidence missing or unverifiablePASS
G12deployment violates a mandatory trust assumptionBLOCKED — 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

Start with docs/auditor/QUICKSTART.md, then docs/LIMITATIONS.md. Also see the Verification Center.