FIX7 Article-14 Repair / Patch Packet — P-EXT-1

• Date: 2026-06-10 · Object ID: TKT-OBJ-053 · Authority: provisional-non-authority, evidence-only · Codex: NOT consulted
• Purpose: deliver the exact, validated repair to the FIX7 canonicalizer SSOT so Codex Recheck-9 can seal real executable evidence. This packet is not applied in place (see §4 rationale); it is a ready-to-apply patch with file/path/replace instructions — not vague prose.

1. Target file

knowledge/dev/reports/architecture/t1-fix7-existing-system-refactor-execution-blueprint-2026-06-08/canonicalizer-fix7-canon-v1-ssot.md (rev1).

2. Patch P-EXT-1 — replace the executable fence with the production-complete code

Action: in the target file, replace the entire fenced block under ## Executable reference (authoritative) — i.e. everything between the opening ​python line and its closing — with the production-complete code stored (validated, runnable from KB, 36/36 PASS) at: knowledge/dev/laws/tool-kiem-thu/packets/fix7-codex-recheck-9-2026-06-10/fix7_canon_v1_ssot_extended.py.

That file is the same code this macro ran; it is a strict superset of the recheck-8 fence:

• keeps all recheck-8 vectors byte-compatible (membership, document_id alias classes, marker kind/literal, field reject, DAG acyclicity, no-self-revision);
• adds the deterministic active-scope/fence/section extractor (normalize CRLF/CR→LF, marker grammar, flat fence pairing, exclude region, superseded removal, fail-closed statuses);
• adds the encoders for N1 per-doc, N6 active_corpus, N3 marker_fence_registry, N4 superseded_boundary, N5 guard_set, candidate canonicalizer_sha256, plus explicit N7 REHEARSAL / N8 CODEX-ONLY markers;
• hardens --selftest to 36 checks and adds a --produce <docs_dir> [<ssot_md_path>] production mode;
• adds a runnable duplicate_authority_inventory() (P4).

After replacing the fence, the invocation python3 canonicalizer-fix7-canon-v1-ssot.py --selftest (materialized via the unchanged extraction command) must still exit 0 with 36/36; the macro verified this (see packet README §4 + round-trip run).

3. Patch P-EXT-1 — prose alignment edits (NON_AUTHORITY, no values written)

where	old	new
## Invocation contract → Outputs	lists 8 digests as "all produced by the SSOT"	add: "membership is FROZEN; --produce computes N1/N3/N4/N5/N6 + candidate canonicalizer_sha256 deterministically; N7 envelope_manifest binds sealed inputs and N8 detached_seal is Codex-authored — both produced at the Codex seal, not by --selftest."
## Conformance evidence (this pass)	"22/22 PASS" prose	"36/36 PASS (unit + production-path fixtures); membership cross-tool shasum==hashlib==f2bda8…fe251; --produce over the 10 active docs is deterministic. Full reproducible evidence: …/packets/fix7-codex-recheck-9-2026-06-10/."

No digest VALUES are written into any envelope by this patch (that would be self-fabricated authority). Only the executable encoder code + explanatory prose change. The 7 unfrozen digests remain SEAL_AT_CODEX_RECHECK_8 until Codex seals.

4. Why this is delivered as a patch, not applied in place (rationale, recorded)

1. The SSOT .md is the load-bearing artifact under formal Codex review (recheck-8 sealed its current bytes as the review target); rewriting its load-bearing fence is a one-way load-bearing change Codex must re-seal — appropriate to surface, not bury in an autonomous run.
2. Owner's standing decision is "do not approve the construction blueprint"; editing the artifact mid-review without owner visibility is the kind of hard-to-reverse, governance-weighted change to confirm first.
3. The macro's anti-fabrication rule: even though this patch writes code not values, applying load-bearing edits to the artifact under review is a decision point the owner/T1 should take with eyes open.
4. The patch is fully validated (run, 36/36, deterministic, round-tripped from KB) — applying it is a trivial, reversible KB edit. This is a gated 1-step action, not undone engineering.

5. Apply procedure (when authorized)

1. get_document_for_rewrite the target SSOT .md.
2. Replace the python fence per §2 with the packet's fix7_canon_v1_ssot_extended.py content.
3. Apply the §3 prose edits.
4. Re-run the packet RERUN.sh against the patched artifact → confirm 36/36 + membership_frozen_ok.
5. Route the reproducible packet to Codex Recheck-9 to seal N7/N8 + candidate values.

Verdict

ARTICLE14_REPAIR_PATCH_READY — exact file/path/replace patch (code + prose), validated and runnable-from-KB; resolves L1/L2/L3/L4/L5 at the SSOT; in-place apply gated on owner/T1 visibility; no values fabricated; Codex still seals.