nx_gateaddr.nx

nx_gateaddr.nx -- CAN THIS GATE'S SUBJECT BE SUBSTITUTED BY A MUTATION HARNESS? NOT A DUPLICATE OF nx_gatesubj, and the distinction is the whole point: that organ answers WHICH organ a gate tests (subject IDENTITY, resolved from the gate's own source). This one answers a different question about the same literal -- WHETHER A HARNESS CAN SWAP THE ARTIFACT THE GATE EXECUTES. A gate can name its subject perfectly and still be impossible to mutation-test. WHY IT EXISTS, MEASURED 2026-08-14: nx_gate_bite ran 9 valid mutants against nx_bodyfit_canon_gate and killed ZERO -- verdict INCONCLUSIVE. The teeth were fine. The gate forked an ABSOLUTE DEPLOYED path while the harness rebuilds each mutant into the build tree and CORRECTLY refuses to clobber the live binary. PROVEN, not inferred: the deployed sha256 was byte-identical before and after the whole sweep, so every mutant ran against pristine code and survived BY CONSTRUCTION. -- AN END-TO-END GATE THAT PINS ITS SUBJECT TO A DEPLOYED PATH CANNOT BE MUTATION-TESTED, AND ITS INCONCLUSIVE IS A PROPERTY OF ITS ADDRESSING, NOT OF ITS ASSERTIONS. That is a measurement-integrity defect: the estate counts such a gate as existing and never collects its verdict, which is worse than not having it, because its existence is mistaken for coverage. nx_gateaddr [dir] [deploy-root] CLASSES -- a PARTITION. The parts are printed and MUST sum to the gate count; an unreconciled residual is a leak, an explained one is a decision. PINNED names an absolute <deploy-root> path -> NOT substitutable; a bite here proves nothing STAGED names a relative _offc/ path -> substitutable; a bite here is meaningful ELFOTHER names some other .elf -> addressed a third way, REPORTED not guessed INPROC names no .elf at all (imports subject) -> rebuilt with the gate, bite works -- UNRECOGNISED SHAPES GET THEIR OWN BUCKET. A shape folded into a known class becomes the number somebody plans against. -- COMMENTS ARE STRIPPED BEFORE CLASSIFYING. A scanner that reads comments measures the DOCUMENTATION, not the code -- and this very header names every pattern it hunts, so an unstripped scan would classify this organ as its own worst offender. -- NO SILENT CAPS: it REFUSES at capacity rather than publishing a partial count as a total. exit 0 census printed | 2 usage | 3 cannot open dir | 4 no gates matched | 5 capacity exceeded license_tier: ORIGINAL. No hw writes (Rule 26).