nx_reclaim.nx

nx_reclaim.nx -- composed reclamation operation. Per [[feedback-reclamation-doctrine-captain-moroni]]: the operation that turns commodity hardware (Intel ME / AMD PSP / baseband / vendor BMC) into substrate that's safe for chosen niches while hostile components remain visible+contained. THIS IS THE BRIDGE PRIMITIVE between the optimization-layer work (nx_organism / nx_symbiote / nx_treaty / nx_budget / nx_homeostasis) and the sovereignty-doctrine work (nx_attest_silicon / nx_xenocell / the 8 reclamation mitigations / the immune tier-1 primitives queued). nx_reclaim COMPOSES THEM. Given a hardware target, it: 1. Calls nx_attest_silicon to learn the chip's threat surface and applied mitigations -> computes effective trust ceiling 2. Instantiates an nx_xenocell for each known hostile component 3. Registers the xenocell with the caller-supplied organism so its observed consumption gets counted into host pressure 4. Computes a safety envelope: what's safe-for-this-chip (gameplay/content/dev) vs unsafe (secrets/identity/PII) 5. Returns the envelope so the caller can decide what cells to run on this host AND what cells to refuse Per the Captain Moroni discipline: we don't ABANDON commodity hardware (that would cede ground to vendors who profit from helplessness). We RECLAIM it for chosen niches by applying every available mitigation + making every adversarial action visible. Composes: nx_attest_silicon -- chip threat surface lookup nx_xenocell -- hostile component wrapping nx_organism -- ecosystem registration nx_budget -- per-niche budget caps from trust ceiling nx_evict_journal -- reclamation events logged V1 ships the synchronous composition. V2 will add ongoing- monitoring loops that re-evaluate the envelope when mitigations change (e.g., user disables an egress filter -> trust ceiling drops -> sovereignty-critical cells refused mid-session).