nx_rosterconf_lib.nx

nx_rosterconf_lib.nx -- WHICH CONFS ARE GATE ROSTERS, AND IS A GATE A ROW OF ONE (2026-09-18, ecosystem EC57). THE DEFECT THIS CLOSES: the heavy roster (knowledge/gateroster_heavy.conf, clock row gaterosterheavy) runs its gates into the SAME production journal as the main roster, while the two organs that ask "does a roster run this gate" each read ONE conf by name: nx_rungclose printed rostered=0 for a gate the heavy beat runs daily, and nx_execsurface credited it no roster surface. A NAME LIST OF CONFS WOULD LAG THE NEXT ROSTER THE SAME WAY, so the list is DERIVED from the resource that causes the execution: a ROSTER is a (conf, journal) PAIR -- the runner's default pair (what `beat` reads and writes when it names neither) plus every pair a clock row runs through `nx_gate_roster_run beat <conf> <journal>`. A third roster is read by declaring its clock row -- no edit here and none in any consumer. THE JOURNAL IS HALF OF THE PAIR (measured 2026-09-18 on the live plane: four beats, and two of them -- gateroster-slow and nofloatslow -- write knowledge/status/gateroster_slow.jrnl and nofloat_slow.jrnl, each keeping its own heartbeat beside its journal, so they must NOT be repointed onto the shared one). A reader that credits a roster must read ITS journal: the close ruler proves TESTED and OPERATED from the production journal plus the journal of every pair whose conf lists the gate, so a slow beat's evidence is read where that beat writes it. RCF_META_OTHER still counts the beats off the production journal. ONE GRAMMAR, MIRRORED FROM ITS AUTHORITY (nx_gate_roster_run.nx: main's argv parse, grr_load, grr_isid), so every organ that asks reads a conf exactly the way the beat that runs it does: a beat the program nx_gate_roster_run (any path, .elf or not; a longer or PREFIX name is another program) with the verb beat; its next argument, when present, is the conf (else RCF_CONF_DEFAULT) and the one after it the journal (else RCF_JRNL). trial and admit run candidates and argless runs nothing, so none of them names a roster. a row leading spaces skipped; a line opening with # or ; is a comment; the gate is the maximal run of name characters [A-Za-z0-9_./-] from there -- so an @directive names nothing, a CR a row carries from another host ends the name, and a longer or PREFIX name is another gate. Pure: every function takes buffers and numbers, so a gate drives it in-process (nx_rungclose_gate). license_tier: ORIGINAL No hw writes (Rule 26).