nx_antibody.nx

nx_antibody.nx -- adaptive defense generation. Per [[feedback-unified-immune-architecture-three-tier]] item 2.7: "adaptive defense GENERATION from observed attacks; the substrate's defensive judo. Captures real attack samples → processes into machine-readable defense definitions → affinity-matures across encounters → distributes via peer mesh → composes legal/social defense materials. Biology: clonal selection + affinity maturation + memory cell formation. Defensive-only discipline: NEVER initiates contact with attackers; only learns from contact attackers initiate." Per [[feedback-cell-immune-system-ransomware-judo-ddos-by-bit]]: the judo is of INFORMATION not retaliation. We never attack back; we make every attacker action visible + analyzable + distributable. Per [[feedback-captain-moroni-doctrine]]: DEFENSIVE ONLY. Substrate refuses to compile offensive antibody operations -- antibodies are detection signatures, not exploitation payloads. Lifecycle of an antibody (clonal-selection analog): 1. nx_pamp or nx_pamp_meta detects an attack -- attack sample captured into nx_xenocell signed observation 2. nx_antibody_generate distills the sample into a detection signature (hash + kind + Q10 affinity) 3. Antibody added to nx_antibody_array; nx_crispr-style memory 4. On each subsequent encounter, antibody's hit_count increments and effectiveness Q10 updates (affinity maturation) 5. V2: antibodies above effectiveness threshold federate via peer-mesh (Citizen Lab analog -- community-shared intel) 6. V2: antibodies compose into legal/social defense materials (sub-poena docs, public advisories) via nx_evict_journal forensic chain Composes: nx_pamp / nx_pamp_meta -- detection feeds antibody generation nx_xenocell -- attack samples come from signed observations nx_crispr -- adaptive memory mechanism reused for antibodies nx_lysis -- antibody confirms threat -> lysis selects mechanism nx_restriction -- antibody-positive input refused at IO boundary