KB-61C5 rev 2

Checkpoint — FIX7 N-Node Authority Model Clarified (2026-06-11)

4 min read Revision 2

tool-kiem-thufix7n-nodecheckpointauthority-model2026-06-11

Checkpoint — FIX7 N-Node Authority Model Clarified

Date: 2026-06-11 Asia/Ho_Chi_Minh · Host: T1 · Codex consulted: NO · Production mutation: NO
Macro: FIX7_N_NODE_AUTHORITY_MODEL_CLARIFICATION_DESIGN_ADDENDUM_MACRO_2026_06_11
Final status: FIX7_N_NODE_MODEL_CLARIFIED_READY_FOR_NEXT_MACRO (carries a material-contradiction finding MC-1/MC-2 on node numbering, documented and resolvable without code/prod/seal).
Real N7/N8/P7 authored: NO/NO/NO. Real N6 chain produced/sealed: NO. Seal claimed: NO.

Decision

The N-node model was reverse-documented from real sources (S1..S17) into a human-readable design addendum + machine-readable JSON. The engineering DAG is consistent and acyclic (has_cycle=False); the only inconsistency is node labelling across three surfaces (blueprint doc 00, canonicalizer SSOT code, authority-seal encoder spec), centred on N1/N2 (MC-1) and N9 (MC-2). No contract defect remains; the only seal-blocking gaps are authority/provenance/owner (G-AUTH-1 SEAL_REAL_N6_NOT_AVAILABLE, G-AUTH-2, G-OWNER-1).

What was done

Live-read 17 sources (canonicalizer SSOT rev3 49c386a9…; blueprint doc 00 §seal-hash-graph; authority encoder spec rev2 + N7/N8/P7 rosters; provenance validation report; 3 Codex reviews; blocker ledger rev7; recheck-6/7 DAG lineage; rehearsal artifacts).
Built a source-discovery table (defines/uses/implies/provenance/conflict/authority-level).
Traced every N1..N9 + the un-numbered membership digest + the authority-layer P7; marked the contradictory/undefined ones explicitly (N9_DIAG = UNDEFINED_NAME in code).
Documented the DAG, the 6-class provenance model + 2 allow-lists, and a dedicated N6 special analysis.
Classified gaps (documentation vs authority vs owner) and produced a next-macro recommendation.

Key findings

MC-1 (material, non-exploitable): N1 = per-doc content (S1/S2) vs membership (S3); N2 = membership (S2) vs canonicalizer_sha256 (S3) vs un-labelled (S1). The seal still binds both membership and canonicalizer hash — nothing dropped — but the N-number→value map is not a single SSOT.
MC-2 (low): N9 named codex_checkpoint_content_sha256_excluding_seal (blueprint) vs N9_DIAG unnamed (code) vs absent (authority). All agree it is a non-load-bearing diagnostic sink.
N6 is active_corpus_sha256 (aggregate corpus proof), not contradicted, value computable today (d777e87c…), "REHEARSAL" only by lane-wiring + provenance class; real path is gated SEAL_REAL_N6_NOT_AVAILABLE, not missing/dead.
No contract defect remains (value-grammar/report-set/provenance/cycle guard all closed). Seal blockers are authority/owner only.

Deliverables (all governed, KB-native)

designs/fix7-n-node-authority-model-design-addendum-2026-06-11.md + .json
reports/fix7-n-node-source-map-report-2026-06-11.md
reports/fix7-n6-special-analysis-report-2026-06-11.md
reports/fix7-n-node-gap-contradiction-report-2026-06-11.md
reports/fix7-n-node-next-macro-recommendation-2026-06-11.md
checkpoints/checkpoint-fix7-n-node-authority-model-clarified-2026-06-11.md (this)
current-state/reports/fix7-n-node-authority-model-clarified-2026-06-11.md
governance/fix7-n-node-authority-model-new-object-governance-update-2026-06-11.md (TKT-OBJ-208..216; deconflicted from T2 lane's 201..207)

Boundaries honored

NO seal/encoder patch · NO real N6/N7/N8/P7 · NO Codex call · NO FIX7 implementation · NO production/PG/Directus/registry/system_issues mutation · NO REAL_RUN/QT001/apply/permit/activation/repoint/cutover · NO registries-pivot · NO auto-birth repair · NO invented node definitions (undefined nodes marked, not inferred as fact). The paused macro …REAL_N6_PROVENANCE_CHAIN… was NOT continued.