Site IntegrityStrong architectural inferencev1.22.1
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.
Measurement and Drift
Evidence levelStrong architectural inferenceTechnical label: Architectural inference
A deployable package can pass local tests and still drift after installation because WordPress routing, hosting configuration, search indexing, and live assets can differ from the local runtime.
Direct answer
After deployment, measure whether the live site matches the package: routes return 200, canonical URLs resolve, sitemap URLs are reachable, discovery files point to Cognivirus.com, answer summaries are accurate, JSON-LD matches visible pages, and users can reach the contact path.
30-day checks
- Verify
/,/contact,/site-integrity,/sitemap.xml,/robots.txt,/llms.txt, and/.well-known/ai-ready.jsonlive. - Submit the sitemap to webmaster tools.
- Run a crawler against the live domain.
- Test keyboard navigation and reduced-motion behavior.
- Ask common answer questions and compare generated summaries to canonical routes.
60-day checks
- Review search queries and rewrite unclear titles or descriptions.
- Fix routes that answer systems misinterpret.
- Review source summaries for outdated labels.
- Confirm that the root package and WordPress package remain version-aligned.
90-day checks
- Publish a route-drift note.
- Review structured data parity.
- Re-run accessibility and sitemap checks.
- Decide whether any optional discovery features should be removed, promoted, or left advisory.