ReferenceArchitectural inferencev1.10.0
Apex threat concepts map
Evidence levelArchitectural inference
This map connects report-derived terms to the site's established vocabulary. It keeps metaphor boundaries explicit and routes readers to public-safe pages.
| Report-derived term | Cognivirus.com term | Evidence posture | Primary page |
|---|---|---|---|
| self-replicating module | functional persistence through successor components | architectural inference | Algorithmic Reproduction Taxonomy |
| multi-LoRA apex threat | adaptive adapter ecology | architectural inference | Apex Pattern Library |
| algorithmic mitosis | near-copy successor creation | metaphor only | Algorithmic Reproduction Taxonomy |
| algorithmic meiosis | recombination or model merging | metaphor only | Model merging |
| skill composition risk | unsafe transition between benign skills | emerging evidence | Skill Composition Risk |
| endogenous yardstick drift | evaluator drift under adaptive pressure | architectural inference | Endogenous Yardstick Drift |
| memory worm | persistent memory as active reservoir | emerging evidence | Persistence Reservoir Layers |
| aggressive mutualism | dependency capture risk | speculative scenario | Human Agency and Mutualism Safeguards |
| execution-time kernel | externalized fail-closed boundary | architectural inference | Execution-Time Boundaries |
Naming rule
Terms from reports can be used when they clarify architecture. They should not be used to imply consciousness, biological life, inevitable catastrophe, or literal viral reproduction.
Maintenance rule
When a new report introduces a dramatic term, add a concept map entry that states:
- the site-safe equivalent;
- the evidence label;
- the metaphor boundary;
- the related control;
- the public page where the term is explained.