nx_nxeconform_gate.nx

nx_nxeconform_gate.nx -- NXE FORMAT CONFORMANCE (constitution A2: NXE, NOT ELF). THE DEFECT THIS EXISTS TO MAKE UNSHIPPABLE (measured 2026-08-15, full population, 23,181 files): NXE had forked into THREE on-disk layouts across TWO magics -- NXE1@80 (the prototype the rule-15 DRY extraction left behind), NXE1@96 (the live lane, and F103a's own witness for C01/C02/C11), and NXE0@64 with a WRAPPING SUM for the kernel image. Nobody was counting, because no instrument counted. * A FORKED FORMAT OUTLIVES THE CODE THAT FORKED IT, BECAUSE THE ARTIFACTS PERSIST. * A LAW THAT MUST BE RECALLED AT THE MOMENT OF TEMPTATION IS NOT A CONTROL; ONLY A MECHANISM IN THE PATH IS -- so this is a gate, not another paragraph. SUBJECT: every NXE artifact ON DISK under the declared roots, classified against the declared layouts. It reads BYTES, never source prose -- a scanner that reads comments measures the documentation. NO HARDCODED NUMBERS: every offset, header size, magic and baseline is a row in knowledge/registry/nxe_layouts.conf (rule 11). The layout/root tables are sized from the conf's OWN line count, so even the table capacity is derived rather than guessed. NO SAMPLING: the roots are swept RECURSIVELY and IN FULL; getdents64 is looped until it returns 0 (one call is not a directory listing), and the single genuine bound -- the directory frontier -- REFUSES at its cap instead of silently truncating (a cap reached in silence becomes a measurement nobody knows is partial). HONEST THIRD STATE: absent conf, zero declared layouts or zero artifacts end the run SKIP via gv_need, never GREEN and never RED -- "I could not look" is not "I looked and it is fine". RATCHET, NOT PERFECTION: three layouts exist TODAY, so a gate demanding one would be permanently RED and everyone would learn to ignore it. The declared-layout count and the weak-integrity count are ratchets that may only FALL. Convergence = delete a LAYOUT row and lower its RATCHET in one edit. THE IMPRECISION I CHOSE TO LIVE WITH, stated so the next reader does not mistake this for exact: (1) A ratchet baseline is DECLARED, so adding a LAYOUT row and raising its RATCHET in the same edit passes. That is deliberate -- the gate's job is to make a widening VISIBLE in the diff and impossible to do by accident, not to prevent a considered decision. (2) The population is artifacts ON DISK under the declared roots. An NXE emitted somewhere no ROOT row covers is outside the claim; that is why the roots are data and the sweep is exhaustive within them. "0 undeclared" always means "0 undeclared, in what was swept". argv[1] optionally overrides the conf path (pinned at registration). Exit 0 GREEN / 1 RED. license_tier: ORIGINAL No hw writes (Rule 26): reads a conf + artifact bytes, writes stdout only.