FIX7 Recheck-9 — KB-Native Packet Completeness Report (R9-B4)

• Date: 2026-06-10 · Authority: provisional-non-authority, evidence-only. Codex consulted: NO · Production mutation: NO.
• Packet root: knowledge/dev/laws/tool-kiem-thu/packets/fix7-codex-recheck-9-2026-06-10/

1. The V1 defect (Codex evidence)

KB packet root returned not_found for RERUN.sh, HASH_MANIFEST.txt, and all raw logs; the KB manifest.json diverged from the locally generated one; the runnable packet existed only as a local mirror — a local mirror is not authority (Article 13).

2. The V2 governed surface — every required file at the KB packet root

KB document (relative to packet root)	rev	role
README_FOR_CODEX.md	16	explanation + rerun/reconstruction instructions
RERUN.sh	1	strict 10-gate rerun (R9-B3)
HASH_MANIFEST.txt	1	28-entry sha256 manifest, bidirectional coverage
manifest.json	4	authority (recomputed fail-closed) + explanatory
manifest_tool.py	2	emit/verify/scan/complete/emit-hash-manifest
adversarial_suite.py	1	12 tamper classes + 4 positive controls (negative-test evidence, executable)
kb_fetch_reconstruct.py	1	fresh-fetch reconstruction tool (read-only; no key embedded)
evidence/canonicalizer-fix7-canon-v1-ssot.md	1	PATCHED SSOT bytes == blueprint-path SSOT rev3
evidence/canonicalizer-fix7-canon-v1-ssot.py	1	materialized fence
evidence/fix7_canon_v1_ssot_extended.py	1	extended reference (byte-identical to fence)
evidence/materialize_canonicalizer.py	1	P1 extraction command
evidence/selftest-expected-output.txt / produce-expected-output.txt	1/1	byte targets for RERUN diffs (expected outputs)
logs/materialized-selftest.log, logs/extended-selftest.log, logs/produce.log, logs/forbidden-scope.log	1	raw sealing-run logs (pinned in manifest authority) — forbidden-scope proof included
logs/manifest-verify.log, logs/adversarial-suite.log	1	post-emit raw logs (pinned by HASH_MANIFEST; manifest-pinning them would be circular — documented)

The 10 active members are NOT duplicated under the packet root: the governed source is the 10 CANONICAL blueprint document ids under knowledge/dev/reports/architecture/t1-fix7-existing-system-refactor-execution-blueprint-2026-06-08/ (one authority, one nature). Their bytes are pinned by HASH_MANIFEST.txt + manifest.json authority, so any live-corpus drift fails the packet closed — by design.

Divergent representations eliminated: the old root-level fix7_canon_v1_ssot_extended.py KB doc (whose header NOTE diverged from the local mirror — part of Codex's R9-B4 evidence) was DELETED (status: deleted, rev 3). One packet representation remains.

3. Fresh-fetch reconstruction proof (executed)

python3 kb_fetch_reconstruct.py /tmp/r9v2-reconstruct
→ 28 files fetched from KB (19 root + 10 docs from canonical ids − HASH_MANIFEST itself verified in place)
→ RECONSTRUCTION: OK (… tree matches HASH_MANIFEST bidirectionally)   exit 0
cd /tmp/r9v2-reconstruct && bash RERUN.sh
→ RERUN_RESULT: PASS (all 10 gates re-executed and enforced)          exit 0

Packet tree hash (relpath + bytes over the tracked tree):

• sealed local packet: 21752e19c76f76613ba1680b734686c558a130e05d64dbc9eb5131b822fba480
• KB-reconstructed tree: 21752e19c76f76613ba1680b734686c558a130e05d64dbc9eb5131b822fba480 → IDENTICAL

Byte-fidelity of the KB store was probed first (then the probe doc deleted): tabs, trailing spaces, consecutive blank lines, non-ASCII (incl. the homoglyph ⁄ used by selftest vectors), and a missing final newline all round-trip exactly.

Fail-closed behavior of the reconstruction: a missing KB packet file returns a 404 error payload (no content) → the tool raises FETCH_FAILED (SystemExit, nonzero); a fetched-vs-pinned hash mismatch or an unfetched HASH_MANIFEST entry → RECONSTRUCTION: FAIL, exit 1.

4. Sealed packet hash tree (HASH_MANIFEST.txt, 28 entries)

cea5ccd73d2e5f94b96c0d6a98ecace6a77a6dbc0cf3051ef9442626f0ebeac8  README_FOR_CODEX.md
562a1f48bdf474973a1eaa868c252f0b91b4e49204873b5c93df7cf635a862e7  RERUN.sh
d80134268a92ce452ef834dd6ac4f227ed62d11d980ee1a8151fc9777ddc46f7  adversarial_suite.py
aae97ad59afd706d1cf004d5e1a64b2796c1ae298fe26c328c4c7701c9d1373e  docs/00-readme-first.md
523f67ece22b7981ff2bce7f089a0d101c3e5b1fa62c50c08fff79156a665cb8  docs/01-live-existing-system-inventory.md
877cb7963ff51ed5afffb8f2bbd2416ed5ee7de45f502d329d9b3aec71fce86b  docs/02-design-to-live-mapping.md
b2ddb5ed96a82e26c40357a71b2ebccf2338576f7ecb950b9762b304714451ad  docs/03-gap-classification.md
610ebd154ca0652dcacf9427c0a16360c0c1b143e88f2646441cd66a8f6b0d40  docs/04-dependency-safe-construction-order.md
f1b8dfca5827dfff0ef457662ba837b5c8cf623f7d589f1d110c4228c9dd1ef4  docs/05-rollback-blueprint.md
227e0fabe2b5b1eb67af65568c574c04926feefcbd0f461989ddb230f7b0e8f0  docs/06-test-guard-blueprint.md
97d1247bc40f0870c7fc78ee331a933300c3748935d8eafd45c1bc283553a356  docs/07-implementation-package-split.md
5d463c411902fa0fb6dca23e3c1903085163e9e032652bae5c60bcf7557852cf  docs/08-hard-blocks-do-not-touch-list.md
31a2fd7ebf7988a09fb4f1ebcf98e84408c815bc694c86fe5a98118534e8eaae  docs/12-final-verdict.md
49c386a9b9666c09786fc4f89bc79776b6046eaee6f4da6d8537d2c753b734d0  evidence/canonicalizer-fix7-canon-v1-ssot.md
d9caa9fe9f46854c38c996747d50d2e73bc5074705730e869fd6b1f8cc26f3e5  evidence/canonicalizer-fix7-canon-v1-ssot.py
d9caa9fe9f46854c38c996747d50d2e73bc5074705730e869fd6b1f8cc26f3e5  evidence/fix7_canon_v1_ssot_extended.py
9e05d2c1b19fc401908c40fed642af6211ee351a4960ba046e805c6a08b9a7a6  evidence/materialize_canonicalizer.py
a860e0362d792c3eb6f3b9b1d2edc334fc24445f0e98cdc137043e3cb4eb2afe  evidence/produce-expected-output.txt
9d5484a76e88bc159a1ab6f737c4f72a918c5e797ce164161761a001e868fa38  evidence/selftest-expected-output.txt
7791b1d07882186f2a010a77adec30d2be952999113404bb07287a02f3456960  kb_fetch_reconstruct.py
a09409bbc1e21a61a9f079034838fff78c52dc2b9e087aa92b4918d117ae8aac  logs/adversarial-suite.log
9d5484a76e88bc159a1ab6f737c4f72a918c5e797ce164161761a001e868fa38  logs/extended-selftest.log
80cb423021bd89120ece2737f79a2087fb58f7fb7722da83e34e57bc4fc44ebc  logs/forbidden-scope.log
61a957bbfaf0e8d18aeabeb3d50b0b1e5aedf09cb8fb47a87272d3eb3263ba82  logs/manifest-verify.log
9d5484a76e88bc159a1ab6f737c4f72a918c5e797ce164161761a001e868fa38  logs/materialized-selftest.log
a860e0362d792c3eb6f3b9b1d2edc334fc24445f0e98cdc137043e3cb4eb2afe  logs/produce.log
e89e5d18ea3ccc6144c8475d27a400d1a30b43a2355556473a35b1df69a6b40d  manifest.json
00e0321f170a7024c52618976e041fcc902acb158e328476134b0820acb2d925  manifest_tool.py

5. Verdict

R9-B4 CLOSED. One byte-exact governed packet surface; every executable/log/hash-manifest artifact KB-resident; fresh fetch reconstructs the identical runnable tree and passes the strict rerun; no local-only authority remains.