<!-- DOC_STATUS: ACTIVE_AUTHORITY -->

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

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).

UPDATE 2026-06-11 (file-completeness repair). Codex review CODEX_FIX7_N_NUMBER_OR_N6_REJECTED (CODEX-T2-PACKET-INCOMPLETE) showed this audit's original §6 verdict ("No report-claim → missing-file discrepancy") was incomplete: it recomputed sha256(HASH_MANIFEST.txt) and fetched the manifest back, but never asserted each manifest-listed file exists at its packet path. Six files were in fact absent. New §8 file-existence check closes that blind spot; the six are now published byte-exact and the audit re-passes. See v02-codex-found-loadbearing-file-completeness-repair-2026-06-11.md.

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 (re-run 2026-06-11 on repaired packet)

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: after the 2026-06-11 README §3a repair, sha256(HASH_MANIFEST.txt) = 08a17307… (== packet_tree.sha256), confirmed by fetching the KB-published manifest back and hashing it (ALL_BYTE_EXACT: True). The prior pin b221f224… corresponded to the pre-repair README; the 9 non-README pins are unchanged. 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, plus new framework-hardening handoff V02-FW-DUP-MANIFEST (non-blocking). No report cites a blocker absent from the ledger.

6. Discrepancies found (original 2026-06-10)

• Stale local registry copies in ~/tkt-v0.2-hardening-workbench/ (registry_new.json max TKT-OBJ-157, index_local.md) lag the KB. Scratch copies, not governed authority; closed by the governance-index-closure report.
• No report-claim → missing-file discrepancy found. SUPERSEDED by §8 — this was a blind spot, not a clean pass; see §8.

7. Verdict (original)

Report-vs-file consistency for hashes/exits/paths: PASS. (But see §8 for the file-existence gap caught later by Codex.)

8. File-existence check (NEW 2026-06-11 — closes the Codex-found blind spot)

The original audit verified hash-of-manifest but not file presence at packet paths. New check: for every line in HASH_MANIFEST.txt, fetch the file at its review-packet path and hash it; assert present AND hash == pin.

Manifest entry	Present at packet path?	sha256 == pin?
README_FOR_OWNER_AND_CODEX.md	YES	YES (0bd3569e…, post-repair)
commands.sh	YES	YES (8b1a5f83…)
exit_codes.json	YES	YES (83afb142…)
content_bind_oracle.py	YES (published 2026-06-11)	YES (0c582901…)
content_bind_verify.py	YES (published 2026-06-11)	YES (3bdee7d2…)
content_bind_regression.py	YES (published 2026-06-11)	YES (afd07c60…)
content_bind_rerun.sh	YES (published 2026-06-11)	YES (ff36e176…)
content_bind_oracle.json	YES (published 2026-06-11)	YES (a331eb6c…)
sp_probes.py	YES	YES (04098c6a…)
real-sut/fix7_canon_v1_ssot.py	YES (published 2026-06-11)	YES (d9caa9fe…)

10/10 present, 10/10 byte-exact. Fresh KB reconstruction into a clean temp dir: shasum -a 256 -c HASH_MANIFEST.txt → 10/10 OK exit 0; backward (no unlisted) OK; packet_tree 08a17307… matches; bash commands.sh → OVERALL PASS exit 0.

9. Updated verdict

Report-vs-file consistency: PASS (with file-existence check). Every hash recomputes, every PASS maps to a real command exit, every manifest-listed file is present and byte-exact at its packet path, no dangling report path. KB round-trip byte-exact. v0.2 remains NON_AUTHORITY / NOT_PROMOTED.