Checkpoint - T1 FIX7 Blueprint Patch After Codex Recheck 7 (Constitution-14 SSOT)

Date: 2026-06-09 Mode: READ-ONLY production; blueprint KB-document direct-revision only; NO production mutation. Macro: PROGRAM_PATCH_T1_FIX7_BLUEPRINT_AFTER_CODEX_RECHECK_7_CONSTITUTION_14_EXECUTABLE_SSOT_AND_NON_SELF_REFERENTIAL_SEAL

Final status

FIX7_REFACTOR_BLUEPRINT_T1_PATCHED_AFTER_CODEX_RECHECK_7_READY_FOR_CODEX_RECHECK_8

What happened

Codex recheck 7 accepted the deterministic extractor, the N1–N9 content-hash DAG, the invariants/boundary, and no runtime hardcode/PG-first regression — but did not seal: five Constitution-Article-14 / NT14 defects (a design is valid only if the implementation path cannot misinterpret it: one executable SSOT, no duplicate authority, no self-reference, no path alias, no marker ambiguity). T1 patched all five in-blueprint; nothing accepted reopened.

blocker	fix	guard
A revision-layer self-reference	own-revision removed from authority (Option 1); revision NON_AUTHORITY_DIAGNOSTIC; finite ordered seal	G-NO-SELF-REVISION-ANCHOR
B no single executable canonicalizer SSOT	authored FIX7-CANON-V1-CANONICALIZER (executable + test vectors + invocation + I/O + failure statuses + AUTHORING_REQUIREMENT), pinned by canonicalizer_sha256	G-CANONICALIZER-SSOT-ONLY
C duplicate canonical authority	one load-bearing contract; doc 00 sections + all reports demoted to NON_AUTHORITY_EXPLANATION	G-NO-DUPLICATE-CANONICAL-AUTHORITY (= Codex G-CANONICAL-CONTRACT-SSOT-NO-DUPLICATE)
D document_id path alias	exact MCP id byte-for-byte; all aliases rejected	G-DOCUMENT-ID-CANONICAL-MCP
E marker contract	closed kind enum + per-kind literal grammar consistency	G-MARKER-KIND-LITERAL-CONSISTENCY

Guards 58 → 63; guard-quality rule 12. Invariants 27/11/14/7 preserved (SSOT artifact is a pinned construction-document TOOL, NOT an active_corpus member — membership stays f2bda8…fe251 — and not a runtime surface/gate/#20-col/catalog-family/8th-hash-contract). Seal event → recheck 8; SEAL_AT_CODEX_RECHECK_7→_8; parent_recheck_checkpoint_id → recheck-7 checkpoint.

Method change + self-review (the user's standing ask)

T1 built the canonicalizer as real executable code and ran it: python3 canonicalizer-fix7-canon-v1-ssot.py --selftest → 22/22 PASS, exit 0, reproducing f2bda8…fe251 and every rejection status (TAB/null/empty; document_id ./..////empty/backslash/ %-encoded/homoglyph/leading-slash/scope/case; marker unknown/inconsistent/typo; seal self-revision/self-hash edge → cycle detected). The 15 Article-14 adversarial scenarios are computed, not asserted (report doc 07). Article-14 discipline applied: one SSOT, every other description demoted to NON_AUTHORITY_EXPLANATION — the implementation runs the artifact, not the prose.

Blueprint docs patched (read-back verified)

• canonicalizer SSOT artifact: created (rev 1)
• 00-readme-first: rev 31 → 49
• 06-test-guard-blueprint: rev 64 → 70 (63 guard rows verified)
• 07-implementation-package-split: rev 51 → 55
• 12-final-verdict: rev 54 → 64

Output

• Report: t1-fix7-blueprint-patch-after-codex-recheck-7-constitution14-ssot-2026-06-09/00..11 (12 docs).
• This checkpoint + the updated blueprint checkpoint (checkpoint-t1-fix7-existing-system-refactor-execution-blueprint-2026-06-08.md).
• The executable SSOT artifact canonicalizer-fix7-canon-v1-ssot.md.

Boundaries

Implementation, Stage 2.6B, qt001_backfill_permit, REAL_RUN, QT001 apply, manifest activation, repoint, owner/ACL cutover all remain BLOCKED. Production READ-ONLY throughout. Next: Codex recheck 8 only (which seals the canonical envelope incl. canonicalizer_sha256 + writes the Codex detached seal without recording the checkpoint's own revision). Do not claim implementation approval.