nx_unified_conductor.nx

nx_unified_conductor.nx -- THE UNIFIED AUTONOMY-LOOP CONDUCTOR: warden-gated AND resource-governed AND closing REPORT->LOG-NEXT, in ONE beat. Resolves the "two loop drivers" incoherence found by nx_loop_census: nx_conductor_live (runtime/) = WARDEN-gated but FIXED cadence (ungoverned = the 20fps-hard-cap anti-pattern) nx_governed_autoloop (_hdl_build/) = RESOURCE-governed but NOT warden-gated This composes BOTH proven halves + my REPORT->LOG-NEXT bridge into one canonical cycle. Lives in _hdl_build/ because (empirically proven by nx_import_probe, Rule 2) a _hdl_build/ organ CAN import both _hdl_build/ organs (the governor) AND runtime/ organs (the warden + eval-queue) -- so no governor is inline-duplicated (which would be the copy-paste anti-pattern this project's own catalog forbids). EACH BEAT: SENSE host (nx_sysload) -> GOVERN (nx_resource_governor: run only if the polite budget is free, else AIMD back off) -> if free, WARDEN-gate the action (nx_warden_lib: ALLOW additive, DENY a source overwrite -- proving the cardinal gate is live) -> if allowed, do a bounded REPORT->LOG-NEXT (queue an evaluator gap via nx_eval_queue, additive to an isolated store). Journals each beat. SAFE BY CONSTRUCTION: BOUNDED beats (UC_BEATS, testable -- NOT the unbounded daemon; that stays a deliberate later flip), ADDITIVE only (writes an isolated eval-gaps queue + a journal, never a source file -- the warden DENIES that), resource-POLITE (yields to live serving + backs off over the load ceiling), NO Claude in the loop. Also demonstrates the BACK-OFF path at a simulated-busy load (politeness proven, not asserted). license_tier: ORIGINAL genealogy_id: operator-2026-07-03-ultimate-loop + unify(nx_conductor_live, nx_governed_autoloop) lineage_id: nishi_unified_conductor_v1 expect_exit: 0