nx_gateorder.nx

nx_gateorder.nx -- sweeps a source tree asking ONE question it can actually answer: DOES THIS GATE LEAVE A DURABLE VERDICT RECORD AT ALL? The standing form of a one-off /tmp shell sweep. A finding not wired into a standing instrument decays, so the check lives here: repeatable by any seat, on any tree, with no shell. ⚠⚠ORDERING IS DELIBERATELY NOT JUDGED. An earlier version of this organ also reported EMIT-EARLY by comparing the first emit-token offset against the last tooth offset. It was WRONG ON ALL SEVEN gates it flagged, and I filed a sev7 debt against other lanes before checking: the token's first textual occurrence lands on HELPER DEFINITIONS (`func g_log`), on TEST FIXTURES, and on /tmp scratch writes -- and this organ's own gate self-flagged, because the pattern appears in its test-data string literals. ★★★★★TEXTUAL POSITION CANNOT DECIDE EXECUTION ORDER. The one genuine ordering defect in this arc was caught by READING THE LOG (gate printed 41/41 while its log said 23/23), which grep could never do. nx_gateorder [root] default root = runtime exit 0 always (a report, not a verdict) license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0