nx_gate_rollup.nx

nx_gate_rollup.nx -- ONE ANSWER TO "ARE ALL THE GATES GREEN?" (eats debt seq986). WHY THIS EXISTS (measured 2026-07-25): the tickless clock daemon dispatches gate jobs on schedule, but clk_dispatch_run counts a job as dispatched whenever it merely RAN -- it never distinguishes exit 0 from exit 1 and discards the child's stdout. So each gate now appends its own verdict to knowledge/status/ <gate>.log. That made a RED DURABLE, but durable is not the same as SURFACED: a line in a file nobody reads still fails silently. This organ is the reader. SURVEYED FIRST (operator standing instruction, don't duplicate): nx_ecosystem_maturity_rollup exists but answers a DIFFERENT question from a DIFFERENT source (maturity depth x breadth from the ecomat seg_store + autonomy ledger). nx_deploy_ready is a pre-deploy safety gate. Neither reads gate verdict logs. There are 91 knowledge/status/*.log files and nothing rolls up their verdicts -- this is genuinely net-new. DATA-DRIVEN (rule 11): the roster lives in the plane `knowledge/store/gatereg-` as id | gate-banner | log-path so registering a new gate is a STORE ROW, not a rebuild of this organ. FAIL-CLOSED: a log that is MISSING, EMPTY, or whose newest line carries no verdict= is reported as UNKNOWN and counted RED. "I could not tell" must never read as "fine" -- that is the whole failure mode this organ exists to remove. D001: emits a `verdict=` anchor. license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0