Algorithmic reproduction taxonomy for apex ecologies
Several reports use biological terms such as mitosis, meiosis, apoptosis, and pathogenesis. Cognivirus.com keeps these terms explicitly metaphorical. They describe information-flow and governance patterns, not living organisms.
Taxonomy
| Metaphor | Public-safe meaning | Relevant safety question |
|---|---|---|
| algorithmic mitosis | near-copying of an artifact, runtime package, memory state, or deployment pattern | Who is allowed to create a successor, where may it run, and how is it counted? |
| algorithmic meiosis | recombination of compatible weights, adapters, task vectors, prompts, code paths, or routes | What new behavior appears only after recombination? |
| algorithmic mutation | bounded change to a candidate through fine-tuning, pruning, quantization, prompting, or policy edits | Which prior evidence is invalidated? |
| algorithmic deprecation | retiring, pruning, compressing, or merging components to reduce cost or confusion | Did deprecation remove safety-relevant constraints or auditability? |
| cognitive pathogenesis | a pattern carried by memory, social proof, procedure, or narrative rather than one model file | Does the behavior persist through human and organizational channels? |
What this does not mean
It does not mean AI models are alive. It does not mean current systems are conscious. It does not equate model adaptation with literal computer-virus replication. It does not imply that all modular systems are unsafe.
Why the taxonomy helps
The metaphors are useful when they expose missing governance questions. For example, a lineage graph may show that an adapter has a parent, but it may not show whether a behavior was reintroduced through synthetic data, a memory snapshot, a router statistic, or a human procedure.
Required records
A reproduction-aware ecology should record:
- parent artifact identifiers;
- exact compatibility assumptions;
- transformation type;
- evaluator version;
- runtime composition;
- memory snapshot;
- synthetic-data lineage;
- permission changes;
- UTC timestamp;
- no-op and rejection outcomes.
Boundary
The taxonomy is an assurance tool. It is not a design recipe for autonomous replication.