nx_treaty.nx

nx_treaty.nx -- bilateral cooperative resource agreement. THE PARTNERSHIP PRIMITIVE. Per user 2026-05-19: "partnering with steam to improve things like vram usage, disk space usage." A treaty is a declarative, breachable agreement between two parties to share a contested resource on agreed terms. Parties may be: - native cell + native cell (intra-Nishi negotiation) - native cell + foreign symbiote (Nishi + Steam-hosted NMS) - organism + symbiote (whole-Nishi-ecosystem + foreign-program) The structural EXCEED-axis vs OS-level resource limits (cgroups, Job Objects, RLIMIT_AS): those are UNILATERAL ceilings imposed by the host. A treaty is BILATERAL -- both parties consent to share terms and either can renegotiate when conditions change. This is the only structurally honest way to integrate a foreground game with a foreground background-inference workload on the same RTX 5080: they negotiate VRAM share dynamically, not fight over it. Composes: nx_budget -- party budgets supply the negotiation basis nx_attention_class -- treaty priority cap (treaty can only require yield UP the priority hierarchy, never down -- a foreground party can't agree to yield to a background party) nx_symbiote -- foreign-party state + observed consumption nx_evict_journal -- proposals, acceptances, breaches logged nx_organism -- container that holds N treaties across all member pairs V1 ships pairwise treaties only. Multi-party treaties (e.g., {organism, Steam-NMS, OBS-recorder} all agreeing to share 12 GB VRAM with weights 60/30/10) are decomposable into pairwise treaties for V1; a multi-party primitive is queued. Gap list (V1 honest perf verdict): - bilateral only (multi-party decomposes) - no expiration time (treaties last until breach or release) - no automatic renegotiation when budgets change - breach detection is observation-window only (caller invokes nx_treaty_check_breach; no background monitor in V1)