Checkpoint — FIX7 Real-N6 Provenance under TKT v0.2 (2026-06-11)

• Host: T1 / Claude Code. Final status: FIX7_REAL_N6_ENGINEERING_CANDIDATE_READY_UNDER_TKT_V02.
• Codex consulted: NO · Owner approval requested: NO · Production/PG/Directus/system_issues mutation: NO.
• T2 v0.2 framework mutated: NO · Real N7/N8/P7 seal created: NO · Official P7 pin created: NO.
• REAL_RUN/QT001/permit invoked: NO · Tool-Kiem-Thu v0.2 promoted: NO.

What this macro did

Closed the engineering half of the standing blocker SEAL_REAL_N6_NOT_AVAILABLE: materialized a real, non-rehearsal ENGINEERING_VERIFIED_CANDIDATE for N6 = active_corpus_sha256 from governed evidence, proved it under TKT v0.2 conventions, and firewalled it from every authority act.

N6 active_corpus_sha256 = d777e87c73d3b62d36789d9343f346102e98dbf301f2c93f7608470b876b258c
provenance_class        = ENGINEERING_VERIFIED_CANDIDATE
authority               = NOT_A_SEAL  (is_official_pin=false; creates_n7_n8_p7=false)

Evidence (all fresh, from governed KB — not workbench, not prose)

• Fresh KB reconstruction: kb_fetch_reconstruct.py → RECONSTRUCTION: OK (32 recheck-9 files + 10 corpus docs + governed encoder; HASH_MANIFEST bidirectional). Corpus byte-exact despite advanced doc revisions (active-authority content frozen).
• Materialized canonicalizer .py = d9caa9fe… (byte-identical to pinned); selftest 45/45 exit 0.
• --produce over the 10 docs: exit 0, byte-identical to pinned produce output; active_corpus_sha256 = d777e87c…; corpus_ok=True; membership_frozen_ok=True.
• Verifier real_n6_provenance_verifier.py: selftest 14/14; --verify exit 0 → certificate.
• Adversarial probes n6_adversarial_probes.py: 27/27 fail-closed, exit 0; no PASS / no seal / no official digest emitted.
• Authority firewall authority_firewall.py: 8/8 rules hold, exit 0.
• Packet RERUN.sh: RERUN_RESULT: PASS — fresh KB reconstruct + all gates + cert byte-diff + HASH_MANIFEST shasum + packet_tree, all enforced this run.

Packet & digests

• Packet: knowledge/dev/reports/architecture/fix7-real-n6-provenance-under-tkt-v02-2026-06-11/
• packet_tree.sha256 = 43b4914acd52a1c410ac1fb4cd1f09d676f3ab53c4af99204e65c15d752eea23
• certificate sha256 acf8d259…; cert binding 055828db… (recomputed intact).

Reality-check answers (macro §3)

• Real N6 produced? YES. Non-rehearsal? YES. Only engineering candidate, not seal? YES.
• Rehearsal/local/prose-only source accepted? NO. Missing/dup corpus accepted? NO.
• Stale hash / byte-hash mismatch accepted? NO. Missing/REHEARSAL/FORBIDDEN provenance accepted? NO.
• OFFICIAL_PIN without owner/Codex accepted? NO. Cert tamper accepted? NO.
• N7/N8/P7 created? NO. REAL_RUN/QT001/permit invoked? NO. Candidate/rehearsal promoted? NO.
• Any report-only evidence? NO. Any missing actual evidence file? NO. Object ID collision? NO. Production mutation? NO.

Governance

• Live collision check: registry json rev20 (max literal TKT-OBJ-225; 208..216 + 225..240 reserved). This macro allocates TKT-OBJ-241..253 (≥241, above reserved ceiling) — no collision.
• Registered via governance addendum governance/fix7-real-n6-object-registry-addendum-2026-06-11.md (no 55KB registry rewrite); registry md + 00-index pointer added.

Remaining blockers (authority-only; NOT T1, NOT this macro)

1. N-NUMBER-RATIFY — owner/Codex ratify the reconciliation table (engineering convention only now).
2. N7-AUTHORITY-INPUTS — owner/Codex supply approval_event_id / approver_identity / timestamp / owner_blueprint_decision (and Codex N8 signer). Do not exist in this lane.
3. N6-PROMOTE — Codex+owner promote the ENGINEERING_VERIFIED_CANDIDATE to OFFICIAL_PIN and run the real N7→N8→P7 seal (real_n6_available=True).

Next minimal macro

FIX7_N7_N8_P7_AUTHORITY_SEAL_REVIEW_MACRO — route this candidate + the firewall to owner/Codex for the authority half. T1 has no further safe engineering work on real N6 itself.