<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 N-Node Numbering Checker — Bad-Label Probe Report (2026-06-11)

Host: T1. Authority: NON_AUTHORITY. Codex consulted: NO. Checker: …/fix7-authority-n-node-tkt-v02-alignment-2026-06-11/n_node_checker.py (sha 4fdf7d24…), grounded in the governed N-node model JSON. Run: python3 n_node_checker.py → 15/15 PASS, exit 0.

Positive assertions (canonical, must PASS) — all PASS

1. N6 = active_corpus_sha256 ✓
2. N2 = canonicalizer_sha256 ✓
3. N9 diagnostic, not load-bearing ✓
4. membership named 'membership', not numbered ✓
5. N9_DIAG resolves to N9 in alias context ✓
6. membership-as-N2 tolerated in alias context ✓

Bad-label probes (must FAIL closed) — all rejected

rule	probe (mutated label)	expected	actual
R1	N2 := active_corpus_membership_sha256 (no alias ctx)	reject	R1_LABEL_REASSIGNMENT
R1	N1 := canonicalizer_sha256 (swap)	reject	R1_LABEL_REASSIGNMENT
R2	unknown N10	reject	R2_UNKNOWN_NODE
R2	unknown N0	reject	R2_UNKNOWN_NODE
R3	N9 claimed load-bearing	reject	R3_DIAGNOSTIC_AS_LOADBEARING
R4	active_corpus_sha256 claimed as N5	reject	R4_VALUE_WRONG_NODE
R4	canonicalizer_sha256 claimed as N7	reject	R4_VALUE_WRONG_NODE
R6	N9 used as authority input	reject	R6_DIAGNOSTIC_AS_AUTHORITY
R2	N9_DIAG without alias context	reject	R2_UNKNOWN_NODE

Reality checks

• N1/N2 swapped label accepted outside alias context? NO
• N9_DIAG accepted as load-bearing authority parent? NO
• Unknown N10 accepted? NO
• active_corpus_sha256 accepted under wrong node number? NO
• load-bearing node with missing name accepted? NO (R5 enforced)
• diagnostic node accepted as authority input? NO

The checker resolves MC-1/MC-2 to a non-exploitable state: the drift labels still exist historically (and resolve only inside an explicit alias context), but no agent can use a swapped/unknown/diagnostic-as-authority label without a fail-closed rejection. Binding ratification of the canonical numbering remains owner/Codex (G-DOC-1).