Direct Answer Map
Answer systems are more likely to represent a site accurately when the site gives clear, concise answers near the top of canonical pages and then links to evidence, limitations, and deeper analysis.
Direct answer
The answer map gives each common question one preferred public route. It is not a doorway-page system. It reduces ambiguity by pointing readers, search crawlers, and retrieval systems to the same visible answer.
Direct answer → source trail → correction path.
Answer and generative retrieval work only when the answer, evidence, limitation, canonical URL, and review route are visible to humans.
Canonical questions
| Visitor question | Preferred route | First-answer requirement |
|---|---|---|
| What is a cognivirus? | /start-here/what-is-a-cognivirus | Define the metaphor and reject literal-virus claims. |
| Is this a malware site? | /start-here/faq | State that the site is research and does not provide exploit instructions. |
| Why is one safe model not enough? | /composition/safety-does-not-compose | Explain interaction effects and runtime composition. |
| What is the apex threat? | /apex-threat/self-replicating-multi-lora-ecosystems | Explain adapter-level reproduction, composition triggers, selection, and persistence reservoirs at a non-operational level. |
| Why does deletion not prove extinction? | /evolution/behavioral-extinction | Explain descendants, memory, synthetic data, and evaluator residue. |
| Who owns the site? | /contact | Identify Michael Kappel and provide contact routes. |
Editorial rule
A direct answer should fit in a short paragraph, but it must not hide uncertainty. If the claim is report-derived, experimental, or speculative, the answer must say so and link to the relevant evidence or source summary.