Governance Addendum — FIX7 Codex N-number/N6 Targeted Repair (TKT-OBJ-273..288, 2026-06-11)

• Host: T1 / Claude Code. Lane: FIX7_CODEX_N_NUMBER_N6_REJECTION_TARGETED_REPAIR_MACRO_2026_06_11.
• Authority: NON_AUTHORITY governance record. Birthed via addendum (no rewrite of the 60KB registry JSON), per established Tool-Kiem-Thu practice.
• Collision deconfliction (live): max canonical-committed object id = TKT-OBJ-262 (T2 file-completeness 254..262, folded into registry MD header). A concurrent T2 NVSZ lane (project_tool_kiem_thu_v02_nvsz_evidence_escrow_planning_2026_06_11) reserved 263..272 as PROPOSED/PENDING-RECONCILIATION (standalone addendum; blocker V02-NVSZ-GOV-FOLD-1 flags a registry/index write-race, not yet folded into canonical). To avoid collision in all reconciliation outcomes, T1 takes 273..288. Reserved ranges intact: T1 182..200 / 208..216 / 225..253; T2 201..207 / 217..224 / 254..262 (+ T2 NVSZ 263..272 PROPOSED). No collision.

Allocated objects

ID	Object	KB path / sha256
TKT-OBJ-273	Targeted repair report	…/architecture/fix7-codex-n-number-n6-targeted-repair-report-2026-06-11.md
TKT-OBJ-274	Duplicate fail-open closure report	…/architecture/fix7-real-n6-duplicate-failopen-closure-report-2026-06-11.md
TKT-OBJ-275	N-number envelope contradiction closure report	…/architecture/fix7-n-number-envelope-contradiction-closure-report-2026-06-11.md
TKT-OBJ-276	Alignment packet completeness repair report	…/architecture/fix7-alignment-packet-completeness-repair-report-2026-06-11.md
TKT-OBJ-277	Codex rejection probe replay report	…/architecture/fix7-codex-rejection-probe-replay-report-2026-06-11.md
TKT-OBJ-278	Report-vs-file audit (rev2)	…/architecture/fix7-real-n6-report-vs-file-audit-under-tkt-v02-2026-06-11.md
TKT-OBJ-279	Checkpoint	…/architecture/checkpoint-fix7-codex-n-number-n6-targeted-repair-2026-06-11.md
TKT-OBJ-280	Current state	knowledge/current-state/reports/fix7-codex-n-number-n6-targeted-repair-current-state-2026-06-11.md
TKT-OBJ-281	real_n6_provenance_verifier.py rev2	…/fix7-real-n6-provenance-…/real_n6_provenance_verifier.py sha 922e5246…80224385
TKT-OBJ-282	n6_adversarial_probes.py rev2 (P25–P28)	…/fix7-real-n6-provenance-…/n6_adversarial_probes.py sha 0f2c94d3…ce2865dfe
TKT-OBJ-283	Real-N6 packet rev2 (manifest/tree/README/manifest.json/exit_codes/2 logs)	…/fix7-real-n6-provenance-…/ tree 356a0cee…282a8b9b
TKT-OBJ-284	Alignment authority_seal_encoder.py (published byte-exact)	…/fix7-authority-n-node-…/authority_seal_encoder.py sha 13344f92…57144b8
TKT-OBJ-285	Alignment codex_probes.py (published byte-exact)	…/fix7-authority-n-node-…/codex_probes.py sha 112b4ec5…465a3d2
TKT-OBJ-286	N7 envelope rev4 (labels-only)	…/fix7-authority-closure-2026-06-10/n7-approval-event-input-envelope.md 182a6d9f… + .json 138a356b…
TKT-OBJ-287	This governance addendum + codex_replay.py reproduction harness	this doc + …/architecture/fix7-codex-n6-duplicate-replay-probe-2026-06-11.py
TKT-OBJ-288	envelope_conformance_probe.py reproduction harness	…/architecture/fix7-n-number-envelope-conformance-probe-2026-06-11.py

Handoff

TKT-NVSZ-RECONCILE-1 — T2's NVSZ lane reserved TKT-OBJ-263..272 PROPOSED/PENDING (V02-NVSZ-GOV-FOLD-1). When that range is folded into the canonical registry, both lanes coexist cleanly (T2 NVSZ 263..272, T1 273..288); no overlap.

Did NOT

Call Codex · request owner approval · create real N7/N8/P7 seal · create official P7 pin · claim N6 Codex-ratified · claim implementation unblocked · run REAL_RUN/QT001/permit/activation/repoint/cutover · mutate production/PG/Directus/registry-row/system_issues · mutate T2 v0.2 framework · promote Tool-Kiem-Thu v0.2 · broaden into v0.3 · rewrite the registry JSON or 00-index body.