nx_papers_beat.nx

nx_papers_beat.nx -- the paper lane's REGRESSION BEAT body (F1131). ★WHY A BODY AND NOT A SCHEDULER. The ecosystem already has ONE clock: nx_clock_run reads the clockjobs registry (name/interval/organ) and forks each due organ arglessly. Building a second scheduler would be duplication. This is only the BODY the shared clock calls, exactly parallel to nx_ecomat_beat -- one per lane, one clock for all of them. ★WHY IT LOGS. Standing law: a beat with no evidence line is a CLAIM, not a control. Four paper gates were green but ran only when a human invoked them, so nothing would have noticed a regression between sessions. This appends ONE line per beat naming every gate's exit code, so "the gates are green" becomes a checkable record instead of a memory. Each gate is run through _offc/nx_sov_build_run.elf, which BUILDS then RUNS it and returns the gate's own exit code -- so the beat also proves the lane still COMPILES, not merely that a stale binary still passes. Runs from the build root (chdir'd if present). nx_papers_beat [logpath] default knowledge/status/papers_beat.log exit 0 = every gate GREEN; 1 = at least one RED (the clock's caller can alarm on it) license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0