nx_gatelaw_gate.nx

nx_gatelaw_gate.nx -- THE SESSION'S LAWS, MADE EXECUTABLE AND POINTED AT EVERY GATE IN THE ESTATE. WHY THIS EXISTS. Every law below was paid for with a real failure, written into a record, and then RE-DERIVED days later because a record is something you have to remember to read. ★★★★★★ A LAW THAT LIVES ONLY IN PROSE IS ADVICE, AND ADVICE IS ADOPTED AT ADVICE RATES; THE SAME LAW PLACED IN THE PATH IS ADOPTED AT 100%. The estate already proved that with nx_memnew (a pre-flight that only INFORMS survives; one that refuses gets disabled). So this is ADVISORY BY CONSTRUCTION: it names offenders, it does not block anyone. Its verdict is bound to ITS OWN subject -- can it read the corpus -- and never to the fleet's condition, because a permanent RED over thousands of legacy gates is noise, not a work order (the same call nx_gatebuilt_gate made about stale_built). THE LAWS, each traceable to a measured failure: L1 EXIT-CARRIES-VERDICT -- a gate that prints RED and returns 0 makes /api/gate_run report GREEN. MEASURED 2026-08-07 on nx_dwline_roundtrip_gate: "passed 5/11 verdict=RED" served as exit_code=0 verdict=GREEN. L2 HAS-NEGATIVE-CONTROL -- a suite of only positive teeth passes on a subject that does nothing. MEASURED: nx_dwline_e2e_gate's no-g control is the only tooth that would catch debug info becoming unconditional. L3 INHERITS-BASE -- hand-rolled counters drift from the teeth that execute, producing red-by-construction (passed 22/20) or silently-skipped teeth. gv_check increments both, so declared == executed BY CONSTRUCTION. ★ MEASURED ON CODE, NOT ON PROSE: comments are STRIPPED before matching. A scanner that does not skip comments measures the documentation -- that defect once made the whole estate inherit "writer" from a comment in nx_syscalls.nx. --------------------------------------------------------------------------------------------- 2026-08-07 CORRECTION -- L1 WAS MEASURING AN IDIOM AND CALLING IT A PROPERTY. The old predicate was a substring test for "return gv_verdict(" / "return gv_". A gate ending let rc: i64 = gv_verdict(name, ctr, note) sys_exit(rc) carries the verdict to the process exit status MORE strongly than `return` does (sys_exit sets the status unconditionally, and does not depend on what the runtime does with main's return value) -- and the old test called it an L1-VIOLATION. Measured: it falsely accused 13 gates written that same day, whose author then read the offender list and believed it.