KB-15A7

FIX7 N-Node Numbering / Semantic Reconciliation (under TKT v0.2, 2026-06-11)

5 min read Revision 1
tool-kiem-thufix7n-nodereconciliationMC-1MC-2tkt-v022026-06-11
<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 N-Node Numbering / Semantic Reconciliation (under TKT v0.2, 2026-06-11)

Host: T1. Authority: NON_AUTHORITY / engineering-convention PROPOSAL. Codex consulted: NO. Binding status: the canonical table below is PROPOSED, labels-only, NOT owner/Codex-ratified. It changes no edge, no math, no digest (confirmed: encoder sha unchanged 13344f92…). Ratification is required before it is binding (blocker G-DOC-1).

Grounded byte-for-fact in the governed model …/designs/fix7-n-node-authority-model-design-addendum-2026-06-11.json (rev1). No node meaning invented.

Canonical N-number → value table (PROPOSED engineering convention)

node semantic name value type deps aliases / deprecated labels provenance class (real) creator consumers load-bearing? status
N1 normalized_active_content_sha256[d] per-doc digest (S3 mislabels membership as N1) ENGINEERING_VERIFIED_CANDIDATE / OFFICIAL_PIN T1/canonicalizer N6, N7(via) YES engineering, rehearsal-classed in lane
N2 canonicalizer_sha256 (rev3) digest S2 "active_corpus_membership_sha256"; S1 unlabelled ENG_CANDIDATE / OFFICIAL_PIN T1/canonicalizer N7, N8 YES MC-1 locus
N3 marker_fence_registry_sha256 digest ENG_CANDIDATE / OFFICIAL_PIN T1 N7 YES engineering
N4 superseded_boundary_sha256 digest ENG_CANDIDATE / OFFICIAL_PIN T1 N7 YES engineering
N5 guard_set_sha256 (= N1[doc06]) digest tag FIX7_GUARD_SET_V1 reserved (G-IMPL-1) ENG_CANDIDATE / OFFICIAL_PIN T1 N7, N8 YES engineering
N6 active_corpus_sha256 corpus aggregate N1 ENG_CANDIDATE / OFFICIAL_PIN T1 N7, N8 YES candidate d777e87c…; gated SEAL_REAL_N6_NOT_AVAILABLE
N7 envelope_manifest_sha256 manifest seal N2,N3,N4,N5,N6,N1 (approval inputs AUTHORITY_INPUT) Codex(real)/encoder(rehearsal) N8, P7 YES rehearsal-only; real gated
N8 detached_seal_sha256 seal N2,N5,N6,N7 CODEX_AUTHORED Codex P7 YES CODEX_ONLY
N9 codex_checkpoint_content_sha256_excluding_seal diagnostic S1 N9_DIAG (unnamed); S3 absent n/a system/Codex(diag) (none) NO MC-2 locus, diagnostic sink
membership active_corpus_membership_sha256 digest (frozen pin f2bda8ef…) S2=N2, S3=N1, S1=unlabelled ENG_CANDIDATE / OFFICIAL_PIN T1 N7 leaf YES decision: name 'membership', STOP numbering N1/N2
P7 authority_seal_pin_sha256 official pin N2,N7,N8 OFFICIAL_PIN Codex (final) YES authority-layer only; blocked

Edges acyclic (has_cycle=false); topological seal order N1→N2→N3→N4→N5→N6→N7→N8→P7. P7 is authority-layer-only (not in canonicalizer EDGES).

Contradiction resolution

  • MC-1 (N1/N2 reassignment). Three surfaces disagree on what N1/N2 name and on whether membership is N1/N2/un-numbered. Resolution (PROPOSED): N2 := canonicalizer_sha256, N1 := normalized_active_content_sha256[d], and the membership digest is named membership and is NOT numbered. Severity: MATERIAL but non-exploitableblocks_seal_math=false (edges/math/digests are consistent; only the human labels drift). The executable checker now rejects any swapped use outside an explicit alias context.
  • MC-2 (N9 naming). N9 is codex_checkpoint_content_sha256_excluding_seal in S2, N9_DIAG/unnamed in S1, absent in S3 — but all three agree it is a diagnostic sink, not load-bearing, not carried into the authority DAG. Resolution: name it N9 (diagnostic), keep it out of the authority DAG. Checker rejects treating it as load-bearing or as an authority input.
  • CC-1 (historical N7→N8 cycle) already RESOLVED (removed rev2; CYCLE_FORBIDDEN enforces; re-proven by encoder selftest "injected N7→N8 edge detected as cycle").
  • G-IMPL-1 (N5 tag cosmetic) recorded, non-blocking.

What this resolves vs what it does not

  • Resolved at engineering-convention level + enforced by checker: the drift is now non-exploitable — a future agent feeding a swapped/unknown/diagnostic-as-authority label is rejected (15/15 checker, see checker-probes report).
  • NOT resolved (requires owner/Codex): the binding canonical numbering. Per the model, the correction "MUST be ratified by Codex/owner before binding." T1 cannot self-ratify beyond engineering convention ⇒ status NEEDS_OWNER_OR_CODEX_RATIFICATION (G-DOC-1/2/3).

Machine-readable form: fix7-n-node-numbering-reconciliation-under-tkt-v02-2026-06-11.json. Executable gate: …/fix7-authority-n-node-tkt-v02-alignment-2026-06-11/n_node_checker.py.

Back to Knowledge Hub knowledge/dev/reports/architecture/fix7-n-node-numbering-reconciliation-under-tkt-v02-2026-06-11.md