In plain English
This page is part of the technical reference. It keeps the expert detail but starts with a plain-language summary for first-time readers.
- Why this matters: AI risk can come from the whole arrangement, not one obvious model.
- What to look for: data, memory, routes, adapters, tools, evaluators, updates, and rollback paths.
- Technical version below: the expert terminology remains available and is linked through the glossary.
Discovery Files and Manifests
The package includes public discovery files such as robots.txt, sitemap.xml, llms.txt, llms-full.txt, ai.txt, ai-manifest.json, ai-ready-manifest.json, .well-known/ai-ready.json, route inventory, and readiness result files.
Direct answer
Discovery files help machines locate public CognivirusA behavior pattern that can survive, move, or reappear across a changing AI system. Open glossary definition routes and understand boundaries. They do not grant permission to authenticate, post, mutate data, execute AI tools, validate credentials, or bypass local policy. The human page remains the authority.
File inventory
| File | Role |
|---|---|
/robots.txt | Public crawl policy and sitemap pointer. |
/sitemap.xml | Canonical list of indexed public routes. |
/llms.txt | Compact reading map for language-model retrieval tools. |
/llms-full.txt | Longer reading map with route clusters and evidence boundaries. |
/ai.txt | Public AI-use boundary and review route. |
/ai-manifest.json | Site identity, version, route clusters, boundaries, and contact path. |
/ai-ready-manifest.json | Target-site readiness manifest for public discovery and no-opThe decision not to change the system. Open glossary definition boundaries. |
/.well-known/ai-ready.json | Well-known alias for the same target-site readiness data. |
/ai-ready-route-inventory.json | Machine-readable route list generated from the content index. |
Important boundary
These files reinforce the public site. They are not bot-only pages, ranking hacks, or live APIs.