nx_frontier_scan_gate.nx

nx_frontier_scan_gate.nx -- the referee for the autonomous frontier-noticer (nx_frontier_scan). SUBJECT: the DEPLOYED ./nx_frontier_scan.elf, forked per tooth. This is an END-TO-END gate, so nx_gate_bite must be given the 4th argument (subject target) or every mutant survives by construction. WHAT IT PROVES, AND WHAT IT DELIBERATELY DOES NOT: PROVES, deterministically and offline -- the internal deficit signal fires exactly when a rival leads a row we do not exceed; that it stays silent in BOTH directions of "no gap"; that the partition sums; that the seeds come from the domain's own data; that the thresholds are read from the conf and ECHOED so the bar is visible; that a missing board REFUSES by name; and that a run NEVER WRITES THE BOARD IT READS. DOES NOT PROVE -- the outbound half. A gate that fetches the live web on a beat is a gate that hammers the box and goes RED when someone else's server is slow. The network leg's accept rule is the METAHUMAN REPLAY (see the lane-E memory), which is a re-runnable harness, not a beat. That imprecision is stated here rather than left for the next reader to discover. FIXTURES ARE ASSEMBLED AT RUNTIME UNDER /tmp/nx_frontier_scan_gate/ -- a gate must not share its fixture with a production beat, and a detector that scans source would otherwise find its own fixture. Idempotent: every run rewrites every fixture, so the second run reports on the same conditions as the first (A GATE THAT IS NOT IDEMPOTENT REPORTS ON ITS FIRST RUN AND LIES ABOUT EVERY RUN AFTER). 100% sovereign. No hardware writes (Rule 26). license_tier: ORIGINAL expect_exit: 0