nx_wiredclaim_gate.nx

nx_wiredclaim_gate.nx -- THE STANDING TEST FOR "CLAIMED BUT NOT CALLED". WHY THIS EXISTS, from an open sev-8 (1785530277) re-confirmed live 2026-08-15. F881 wired the rule-11 magic-number ratchet into /api/build, that wiring was later LOST, and NOTHING SAID SO. Four source comments went on asserting the enforcement as established fact for months while builds sailed through unchallenged. The debt row names the missing piece itself: "an enforcement with no standing test is how this silently reverted" "IF NO TEST FAILS WHEN THE WIRING IS REMOVED, THE WIRING WILL BE REMOVED AND NOTHING WILL SAY SO." nx_wiredclaim already COMPUTES the answer, but it takes a grep artefact as input, so nothing could put it on a beat. That is the whole gap this organ closes: it is the thing that says so. COMPOSES, NEVER RE-DERIVES: the judgement is nx_wiredclaim_lib's (wc_scan/wc_verdict) so there is exactly one definition of "called vs merely claimed" in the estate. Shaped after nx_sweepgate (same session): fork the proven scanner, READ THE ENVELOPE BEFORE THE NUMBERS, then judge. THE CEILING, STATED UP FRONT: wc_verdict keys on LINE SHAPE -- a non-comment, non-self mention is a call-site CANDIDATE, not proof that anything executes. So WIRED here is necessary, not sufficient, and this gate detects the F881 SHAPE rather than certifying that a chokepoint fires. nx_wiredclaim says the same of itself: confirm by execution. A gate that overstated this would be the false proof with an authoritative name that the estate keeps paying for. license_tier: ORIGINAL Read-only. No hw writes (Rule 26). expect_exit: 0