Incomex AI Portal
KB-74CE

Codex FIX7 Blueprint Recheck 9 — Reproducible Packet Seal Review

11 min read Revision 1
fix7codexrecheck-9reproducible-packetseal-reviewarticle-13article-14needs-t1-fix2026-06-10

Codex FIX7 Blueprint Recheck 9 — Reproducible Packet Seal Review

Date: 2026-06-10
Mode: read-only KB review + safe offline packet rerun in /tmp; report/checkpoint writes only
Final status: CODEX_RECHECK_9_NEEDS_T1_FIX
Production mutation: NO
Seal decision: REJECT / DO NOT SEAL N7, N8, P7, canonicalizer hash, or blueprint approval.

1. Scope

Reviewed only the prompt-defined Recheck-9 packet, handoff/report/blocker ledger, current canonicalizer SSOT, and current 10 active-document identities. Did not implement FIX7, run REAL_RUN, apply QT001, issue permits, activate/repoint/cutover, resume registries-pivot, repair auto-birth, or mutate production.

2. Files read directly

KB:

  • knowledge/dev/laws/tool-kiem-thu/packets/fix7-codex-recheck-9-2026-06-10/README_FOR_CODEX.md
  • .../manifest.json
  • .../manifest_tool.py
  • knowledge/dev/laws/tool-kiem-thu/checkpoints/fix7-codex-recheck-9-final-handoff-2026-06-10.md
  • knowledge/dev/laws/tool-kiem-thu/reports/fix7-p-ext-1-apply-and-recheck9-handoff-report-2026-06-10.md
  • knowledge/dev/laws/tool-kiem-thu/checkpoints/fix7-recheck9-remaining-authority-blocker-ledger-2026-06-10.md
  • current 10 active blueprint docs + current canonicalizer SSOT identity/revision/content length
  • Operating Rules SSOT v7.58; Constitution v4.6.3, Articles 13/14

Offline mirror /tmp/fix7-canon/packet/:

  • RERUN.sh, HASH_MANIFEST.txt, manifest.json, manifest_tool.py
  • canonicalizer/materializer files, 10 pinned docs, raw logs, expected outputs

KB packet-root reads for RERUN.sh, HASH_MANIFEST.txt, and raw logs returned not_found; they exist only in the local mirror used for rerun.

3. Commands run and decisive outputs

3.1 Nominal rerun

bash RERUN.sh
...
ALL PASS: True (36/36 checks)
exit=0
membership_frozen_ok: True
MANIFEST_VERIFY: OK (all 33 recomputable literals == recomputation...)
RERUN_RESULT: PASS
CODEX_RERUN_EXIT=0

Nominal rerun verdict: PASS on the supplied local mirror only.

3.2 Direct manifest verification

python3 manifest_tool.py --verify
MANIFEST_VERIFY: OK (all 33 recomputable literals == recomputation...)
MANIFEST_VERIFY_DIRECT_EXIT=0

3.3 Hash manifest

shasum -a 256 -c HASH_MANIFEST.txt
... all 25 pinned files: OK
HASH_MANIFEST_EXIT=0

3.4 Recomputable-hash tamper

Changed ssot_new_sha256 to zeros on a copied packet:

MANIFEST_VERIFY: FAIL
RECOMPUTABLE_HASH_TAMPER_EXIT=1

This narrow hash-tamper path works.

3.5 Current-pass literal tamper — decisive failure

Changed only:

"forbidden_scope": {"forbidden_operations_found": 999}

Then ran both verifier and full rerun on a copied packet:

MANIFEST_VERIFY: OK (all 33 recomputable literals == recomputation...)
UNVERIFIED_LITERAL_TAMPER_EXIT=0
...
RERUN_RESULT: PASS
RERUN_WITH_UNVERIFIED_LITERAL_TAMPER_EXIT=0

Therefore manifest_tool.py --verify does not verify every current manifest value or every current PASS/seal claim. It verifies a selected 33-value hash subset plus two special fields.

3.6 Missing active document — decisive failure

Removed docs/05-rollback-blueprint.md on a copied packet and ran the declared production --produce path:

05-rollback-blueprint.md EXTRACT_ERROR=LOCAL_FILE_MISSING
membership_frozen_ok: True
MISSING_DOC_PRODUCE_EXIT=0

The production seal path detects the missing document but still exits 0 and reports frozen membership OK. Detection without fail-closed enforcement is not Article-14 proof.

3.7 Canonical identity and nominal hashes

canonicalizer SSOT .md: 144eb3d9f44bc69b0955c387b7f6c3cf5e306a41e9e2716d42ddf2412f87412a
materialized .py:       196d98011b38d32a4046c5565bdd01906ea737a3e304ccf8229dd7c1c7e8dfdc
extended .py:           196d98011b38d32a4046c5565bdd01906ea737a3e304ccf8229dd7c1c7e8dfdc
CANONICAL_PY_IDENTICAL_EXIT=0

4. Exact blockers

R9-B1 — Manifest verifier is not complete/fail-closed

  • Evidence: tampering forbidden_operations_found to 999 still yields verifier exit 0 and full RERUN_RESULT: PASS.
  • Root cause: flatten_hashes() verifies only selected hash-bearing fields; current claims such as forbidden scope, negative-test status, P-EXT apply/revision, counts/classes, authority/status, and remaining blockers are hard-authored or unchecked.
  • Article impact: prose/current-literal PASS remains possible; disguised hardcode remains in current PASS logic.
  • Who acts: T1.
  • Required fix: define a canonical manifest schema and recompute/verify every load-bearing field; separate explanatory fields outside the verified authority object; any unverified load-bearing field must fail verification.

R9-B2 — Production --produce path is not fail-closed on missing active member

  • Evidence: missing doc 05 produces EXTRACT_ERROR=LOCAL_FILE_MISSING, membership_frozen_ok: True, and exit 0.
  • Root cause: membership hashes the frozen IDs independently of successful extraction; extraction errors do not force nonzero exit.
  • Article impact: production seal candidates can be emitted with an incomplete active corpus.
  • Who acts: T1.
  • Required fix: any missing/error/extra/duplicate/invalid active member must suppress all candidate digests and force nonzero exit; add executable negative test asserting nonzero.

R9-B3 — RERUN.sh does not enforce every step exit and does not reproduce all claimed evidence

  • Evidence: script uses set -u, not set -e; selftest and --produce exits are printed but not checked. RERUN does not execute shasum -c, forbidden-scope scan, or the negative tests; it trusts pinned logs/current literals.
  • Article impact: RERUN_RESULT: PASS is stronger than the executed checks.
  • Who acts: T1.
  • Required fix: explicitly capture/check every command exit; rerun hash manifest, forbidden-scope proof, and all negative tests; any mismatch/nonzero/unexpected-zero must fail the rerun.

R9-B4 — KB packet and runnable mirror are not one reproducible authority-bound packet

  • Evidence: KB reads returned not_found for packet-root RERUN.sh, HASH_MANIFEST.txt, and raw logs. KB manifest.json contains fields such as verified_by and input_docs_provenance that the local command-generated manifest does not contain. The local mirror manifest hash is 458460..., while the README's earlier hash listing and KB representation are not the exact local generated object.
  • Article 13/14 impact: Codex reran a local mirror, not a fully re-fetchable KB-native packet; duplicate/divergent packet representations remain.
  • Who acts: T1.
  • Required fix: publish one byte-exact governed packet surface, pin every executable/log/hash-manifest artifact, and prove a fresh fetch reconstructs the same packet hash tree.

R9-B5 — Current KB byte seal cannot be completed

  • Evidence: current KB identities were re-fetched. All 10 current document content_length values and current SSOT rev2 content_length=31301 match the local mirror character counts. However the available MCP read interface did not provide an independently computed SHA-256 of current KB bytes; exact current-byte equality remains unproven. Packet manifest also omits sealed current kb_revision fields for N6.
  • Who acts: T1/KB tooling for evidence; Codex rechecks afterward.
  • Required fix: provide a governed byte-export/hash proof for the 10 current docs and SSOT, bound to document IDs and revisions; no local-mirror-only hash.

5. P-EXT-1 verification

  • Current KB canonicalizer SSOT is revision 2, content_length=31301.
  • Local mirror has the same character count and nominal candidate hash 144eb3d9....
  • Materialized Python equals extended Python and selftest is 36/36.
  • Exact current KB-byte SHA-256 could not be independently recomputed through the available MCP read interface.

P-EXT-1 verdict: PARTIAL / BYTE-EXACT SEAL UNVERIFIED. Do not pin authoritative canonicalizer_sha256 or revision yet.

6. Hardcode / disguised-hardcode verdict

FAIL. manifest_tool.py hard-authors current load-bearing claims and --verify does not check them. The historical ssot_old_sha256 is correctly labelled historical and is not the blocker. Candidate/rehearsal values are correctly labelled non-sealed.

7. Article 13 verdict

FAIL FOR SEAL. The runnable/hash-bound packet exists as a local mirror, while required packet artifacts are not readable from the governed KB packet root and exact current KB-byte hashes are not bound. KB/PG-native authority cannot be replaced by a local packet mirror.

8. Article 14 verdict

FAIL. Nominal rerun is real, but fail-closed proof is false/incomplete:

  • current-pass literal tamper still ends PASS;
  • missing active doc still yields production-path exit 0 and membership_frozen_ok: True;
  • RERUN omits several claimed evidence regenerations and does not check every command exit.

This is not sufficient executable proof for a seal.

9. N7 / N8 / P7 decision

Item Verdict Reason
N7 sealed approval-event inputs/envelope DO NOT SEAL Engineering manifest/corpus fail-closed blockers remain; owner approval inputs also absent.
N8 detached seal DO NOT AUTHOR N7/P7 prerequisites not met.
P7 Codex re-seal REJECT Article 13/14 and packet reproducibility blockers remain.
authoritative canonicalizer_sha256 / revision DO NOT PIN current KB-byte SHA not independently proven.
blueprint approval NOT AUTHORIZED owner's standing do-not-approve remains; engineering defects also remain.

10. Final verdict

CODEX_RECHECK_9_NEEDS_T1_FIX

This is not AUTHORITY_BLOCKED: authority blockers exist, but engineering/evidence defects independently prevent a seal.

11. Minimal safe next step

T1 must issue a corrected Recheck-9 packet that closes R9-B1 through R9-B5, then route it for a fresh Codex rerun.

Back to Knowledge Hub knowledge/dev/reports/architecture/codex-fix7-blueprint-recheck-9-reproducible-packet-seal-review-2026-06-10/00-readme-first.md