nx_law_warden.nx

============================================================================================ FREEZE LIFTED 2026-08-07 -- debt 1785516173 (sev9) is EATEN and the reconstruction is IN THIS FILE. The banner below used to read "STOP -- DO NOT BUILD OR PROMOTE THIS ORGAN", and it had become FALSE AND INTERNALLY CONTRADICTORY: its first paragraph said this source "HAS NONE OF countfile / scancap / gatedry / helperdup / T20" while its own last paragraph said "Already restored here: countfile ...". All of them are present now -- lw_countfile, lw_file, lw_segamp, lw_file_gatedry, lw_file_helperdup, lw_file_scancap -- and each was compiled, linked and RUN standalone with a POSITIVE and TWO NEGATIVE controls before being wired in (see the L009/L010/L011 note below). ★★★★★★A FREEZE NOTICE OUTLIVES THE CONDITION IT DESCRIBES. A DEBT ROW HAS A LIFECYCLE -- open, eaten -- AND NOTHING EVER CLOSES A COMMENT. The debt was closed; the STOP sign stayed up, and any reader arriving here would have believed a live sev-9 freeze that no longer existed. ⇒ WHEN A COMMENT ASSERTS A STATE, IT MUST NAME THE ARTIFACT THAT CAN BE QUERIED FOR THAT STATE (here: `nx_debt show 1785516173`), so the reader can check it instead of trusting it. THE HAZARD THE FREEZE GUARDED IS REAL AND STILL APPLIES -- read this before rebuilding: nx_magicratchet CONSUMES `nx_law_warden countfile` -- but it is NOT reached from /api/build. CORRECTED 2026-08-15 (open sev-8 debt 1785530277, re-confirmed live today). This line used to assert the wiring as fact. Measured two ways: nx_wiredclaim reports CLAIMED-UNWIRED call_sites=0 comment_mentions=17, and behaviourally FOUR /api/build runs of nx_oo_extract_gate left its baseline at -1 while a single direct nx_magicratchet call created one. The chokepoint was exercised; nothing refused. A COMMENT THAT ASSERTS AN ENFORCEMENT IS NOT AN ENFORCEMENT, and this one was load-bearing: it is the stated reason this organ accepts a design constraint in exchange for a guard that is not in the path. If a rebuild ever drops that verb, mr_parse_magic returns -1, the ratchet FAILS OPEN BY DESIGN, and magic-number enforcement plus the hourly autofiler both go silent WITH EVERY GATE STILL GREEN. ⇒ THE MECHANICAL REFEREE, NOT A PROMISE: promote WITHOUT allow_capability_loss. /api/promote compares the new binary's strings against the live one and REFUSES on capability loss, so the guard adjudicates this rebuild rather than anyone's reading of this comment. If it refuses, reconcile -- do not pass the flag to get past it. ★A GATE THAT IS GREEN ON THE BINARY PROVES NOTHING ABOUT THE SOURCE THAT WILL REPLACE IT. ★WHEN SOURCE AND ARTIFACT EACH CONTAIN WORK THE OTHER LACKS, THERE IS NO SAFE DIRECTION. ============================================================================================ nx_law_warden.nx -- MECHANICAL ENFORCEMENT for written laws (ws=cap-autonomy, 2026-07-20). Operator: "make sure autonomously that our nishi ecosystem is getting sota ... what needs to become mcp or api or raci or workflows or agents or other modern capabilities just gets logged and worked without me having to call its need out"; + "our magic number audit and bug stuff dont appear to be autonomous ... lots of workstreams are flagging them as bugs they hit and then just gave a new number to"; + "callouts of using webrtc or webassembly ... not building from the first byte up to a sovereign nishi os and browser". THE GAP THIS EATS: every conformance surface we own is a CURATED manifest -- nx_favela_census states it outright ("unnamed shanty stays invisible until a row names it"). A written law (CLAUDE rule 11, the