nx_firstbyte_gate.nx

nx_firstbyte_gate.nx -- the first-byte-up analysis is DERIVED, its cap axis is MEASURED, its unsound links are RANKED BY ACTIONABILITY, it DISCRIMINATES, and it declares the axis it cannot see. Subject: ./nx_firstbyte.elf (the serving-root binary; e2e fork, never an in-process re-derive). PRE-DECLARED ACCEPT RULE: would this instrument have surfaced the five foundation defects of 2026-08-23 BEFORE the lane above hit them? Known ground truth, so a real validation set. Re-scored after the ranking landed -- published honestly, INCLUDING WHAT DID NOT MOVE: D2 nx_gsplat 512x384 CAUGHT, and now ATTRIBUTED. The splat rungs read NOT-READY with first_unsound=nx_gsplat.nx classed OWN -- the rung's own module, the lane that owns the rung owns the fix. D1 nx_skeleton SK_MAXB=32 MOVED: was CAUGHT-BUT-MASKED, now the mask is GONE and for the right reason -- nx_skeleton.nx reads verdict=CLEAN (capacity_population=0) since the rig-floor lane derived that bound away. It still sits in three chains, and it is named in NONE of them. The tooth below asserts exactly that consistency: A LINK THE CENSUS CALLS CLEAN MUST NEVER BE NAMED AS UNSOUND. (If the skeleton lane re-introduces a picked bound this tooth goes RED -- that is a foundation regression, and it SHOULD be visible here. Named so the next reader knows why.) D3 PF_NB=48 MISS, structural and UNCHANGED: a DATA prior read at runtime is not an import. AN IMPORT GRAPH CANNOT SEE A DATA DEPENDENCY. Asserted. D4 no vector types MISS, UNCHANGED: a LANGUAGE gap has no module to point at. D5 no mesh->skeleton binder MISS, UNCHANGED: no row declared it. EMPTY-CHAIN is the nearest observable proxy and is checked as its own bucket, even at zero. WHY THE RANKING NEEDED ITS OWN TEETH: ranking is a claim about ORDER, and an order can be wrong while every count is right. The load-bearing tooth parses EVERY ranked list and asserts class order (own, then rare, then ubiquitous) with ascending fan-in inside a class -- because the whole point is that A CAP IN A LEAF EVERYONE SHARES MUST NEVER OUTRANK A CAP IN YOUR OWN MODULE. It also counts what it parsed, so a run that parsed nothing cannot pass as a run that found nothing out of order. license_tier: ORIGINAL Read-only. No hw writes (Rule 26).