nx_lysis.nx

nx_lysis.nx -- selective foreign-entity neutralization. Per [[feedback-unified-immune-architecture-three-tier]] item 3: the user's specific question: "take how would you combat and deactivate nano bots as if they were viruses or stuff like that, would a giant magnet work or what is the equivalent that would purge but not hurt the host think of the mechanisms of anti parasites on things like ivermectin or whatever." THE UNIVERSAL PRINCIPLE: selective targeting via host-threat biochemical/physical/electromagnetic/structural differences. Ivermectin works because parasite ion channels differ from mammalian; magnetic-particle hyperthermia works because ferromagnetic threats heat in alternating fields while diamagnetic tissue does not; chelation works because EDTA binds heavy metals preferentially. SOFTWARE SUBSTRATE EQUIVALENT: neutralize the foreign entity by exploiting a difference between FOREIGN and HOST that the host can tolerate. We have several such differences available -- foreign processes lack the substrate's capability tokens, foreign memory pages lack the chromatin chain, foreign egress targets aren't on the substrate's allowlist. Each difference = an attack vector against the foreign entity that costs the host nothing. Mechanism catalog shipped V1 (each = one host-tolerant difference the substrate can exploit): CAPABILITY_REVOKE -- drop the brane capability tokens; foreign loses access without affecting self MEMORY_ZERO -- overwrite foreign memory region with zeros (caller has already isolated the region) NETWORK_BLACKHOLE -- route foreign egress to /dev/null; host egress on other interfaces unaffected PROCESS_PAUSE -- SIGSTOP foreign process (reversible; gathers evidence while frozen) PROCESS_TERMINATE -- SIGKILL foreign process (irreversible) QUARANTINE -- isolate-but-preserve (no kill, no read, operator review gates next step) CRYPTO_REKEY -- rotate the substrate's master keys; any foreign cached credentials become useless