# You are working on Cognivirus.com.

## Public-safe source report summary

This uploaded source report is preserved as durable project evidence for Cognivirus.com. It contributes concepts to the v1.15.0 danger-model expansion: Metaphor boundary, self-reinforcing patterns, distributed persistence.

## Evidence handling

This is treated as a **source dossier**, not as independently verified empirical consensus. Public pages may use it after applying the site evidence ladder, metaphor boundaries, and non-operational safety policy. It must not be used to claim that AI systems are conscious, literal biological viruses, or inevitably catastrophic.

## Concepts extracted for the site

- The unsafe unit may be a transition graph rather than one model artifact.
- Local component approval does not prove runtime-composition safety.
- Evidence should name the exact carrier, route, memory state, evaluator, tool profile, and promotion rule involved.
- Observable outcomes need replayable traces rather than trust language.
- Retirement, rollback, and behavioral-extinction reviews must include data, memory, synthetic examples, descendants, aliases, and human workflows.

## Source orientation

You are working on Cognivirus.com. Your task is to perform a major content-deepening pass on the site. The goal is to make Cognivirus.com explain, in a clearer and more powerful way, the dangers it is already highlighting: distributed AI behavior persistence, unsafe compositions, adaptive model ecologies, selection pressure, synthetic feedback loops, action-layer risk, weak observability, incomplete rollback, and model retirement failure. Do not turn the site into generic AI fear marketing. Do not frame Cognivirus as a literal biological virus, literal malware, or proof that current AI systems are conscious. Cognivirus must remain an analytic

## Site interpretation

The report is used to deepen public and technical explanations of distributed behavioral persistence, synthetic-feedback risk, action-layer controls, observability, lineage, diversity, promotion pressure, and retirement failure. It does not authorize exploit instructions, self-replication recipes, credential workflows, or backdoor construction guidance.