<!-- DOC_STATUS: ACTIVE_AUTHORITY -->

v0.2 Report-vs-File Consistency Audit (2026-06-10)

Authority: NON_AUTHORITY / NOT_PROMOTED · Codex consulted: NO Purpose: every load-bearing claim in the v0.2 reports maps to an actual governed file / command / exit, recomputed against reality (not prose).

1. Hash claims → actual KB files (recomputed)

Claim (in prior reports / memory)	Source of truth checked	Result
verifier fixed = content_bind_verify.py rev2 3bdee7d2…	KB content-binding/CONTENT_BINDING_HASH_MANIFEST.sha256 rev3 line	MATCH
content-binding tree a6a9b314…	KB content-binding/packet_tree.sha256 rev2 = sha256(manifest) (recomputed by reconstruct_from_kb.py: calc==pin)	MATCH
oracle pins content_bind_oracle.json a331eb6c…	KB manifest line + fresh fetch	MATCH
oracle module content_bind_oracle.py 0c582901…	KB manifest line + fresh fetch	MATCH
rerun runner content_bind_rerun.sh ff36e176…	KB manifest line + fresh fetch	MATCH
reconstructor reconstruct_from_kb.py cfdd45fc…	KB manifest line + fresh fetch	MATCH
frozen V3 SUT d9caa9fe…	commands.sh G0 + manifest + canonical doc	MATCH

2. PASS claims → actual command exits (re-run this macro)

Report claim	Command (real)	Exit	Verdict
oracle selftest 12/12	python3 content_bind_oracle.py --selftest	0 (ALL PASS:True 12/12)	confirmed
verifier selftest 14/14	python3 content_bind_verify.py --selftest	0 (ALL PASS:True 14/14)	confirmed
DEV/STRICT/V3 RERUN pass	bash content_bind_rerun.sh DEV|STRICT|V3 (fresh tree)	0/0/0	confirmed
second-pass probes 28/28, 0 fail-open	python3 sp_probes.py (fresh tree)	0	confirmed
review packet 7/7 gates	bash commands.sh	0 (OVERALL_RESULT: PASS)	confirmed

3. Report path existence (KB list)

All six prior Self-Codex reports + checkpoint exist in KB (verified by list_documents on …/reports/ and …/checkpoints/): v02-self-codex-adversarial-proof-report (r1), v02-direct-adversarial-probes-report (r1), v02-failopen-rejection-report (r1), v02-oracle-independence-report (r1), v02-governed-evidence-file-completeness-report (r1), v02-loadbearing-claim-coverage-matrix (r1), checkpoint-v02-self-codex-proof (r2). No report path is dangling.

4. Manifest / tree recomputation

• Content-binding: sha256(CONTENT_BINDING_HASH_MANIFEST.sha256) == a6a9b314… (== packet_tree.sha256). Recomputed by reconstruct (calc==pin). OK.
• Review packet: sha256(HASH_MANIFEST.txt) == b221f224… (== packet_tree.sha256), confirmed by fetching the KB-published manifest back and hashing it (ALL_BYTE_EXACT: True). OK.

5. Blocker coverage

Every blocker referenced by the reports appears in the blocker ledger: V02-PB-CONTENT-BIND-PROMOTE, V02-PB-PRODUCE-CONTENT (engineering-mitigated), V02-PB-NVSZ-1, V02-PB-PROMOTE-1. No report cites a blocker absent from the ledger.

6. Discrepancies found

• Stale local registry copies in ~/tkt-v0.2-hardening-workbench/ (registry_new.json max TKT-OBJ-157, index_local.md) lag the KB. These are scratch copies, not governed authority; the governed registry/index are in KB. Recorded; closed by the governance-index-closure report (registry bumped in KB).
• No report-claim → missing-file discrepancy found.

7. Verdict

Report-vs-file consistency: PASS. No prose-only evidence behind a load-bearing claim; every hash recomputes; every PASS maps to a real command exit; no dangling report path. KB round-trip byte-exact.