nx_gatereg_derive.nx

nx_gatereg_derive.nx -- DERIVE the gate roster from the evidence itself. WHY THIS EXISTS (measured 2026-07-30): knowledge/gatereg.conf listed FOUR gates while the same NAS held 181 knowledge/status/*.log files. nx_gate_rollup can only roll up what the roster names, so "verdict=GREEN pass=4/4" was a true statement about a roster that covered ~2% of the evidence -- a green light with almost nothing behind it. Hand-maintaining that roster is why it never grew. So: stop typing the roster, DERIVE it. A log whose newest line carries a verdict anchor IS a gate log, by the gate plane's own contract; anything else (token_spend.log, resources.log, ...) is not and is deliberately left out rather than registered as a permanent UNKNOWN. READ-ONLY BY DEFAULT. It prints the split (green / red / no-anchor) and the candidate rows, and writes a roster ONLY when given an explicit emit path. Registering a RED gate is correct -- that is the point of surfacing -- but it flips the rollup RED and nx_gate_rollup AUTO-FILES a debt, so the operator sees the count before that happens instead of after. nx_gatereg_derive [statusdir] [emitpath] statusdir default knowledge/status emitpath if given, write "<BANNER>\t<path>" rows for every anchored log The banner is a DISPLAY LABEL only -- nx_gate_rollup reads the log's last line and never compares the banner -- so it is derived from the filename (stem uppercased, '_' -> '-') and cannot be wrong in a way that changes a verdict. license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0