Site IntegrityDemonstrated real incidentv1.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.
Structured Data Parity
Evidence levelDemonstrated real incidentTechnical label: Demonstrated
Cognivirus.com emits WebSite, BreadcrumbList, Article, Dataset, DefinedTermSet, and ContactPage JSON-LD only where those types match visible page content.
Direct answer
Structured data on Cognivirus.com is a mirror, not a second source of truth. If a claim is not visible on the human-readable page, it should not appear as a stronger claim in JSON-LD, manifests, or advisory discovery files.
Allowed structured-data use
| Page type | JSON-LD type | Condition |
|---|---|---|
| ordinary research page | Article | title, description, canonical URL, and modified date match page metadata |
| glossary | DefinedTermSet | terms are visible on the glossary page |
| schema/reference pages | Dataset | page actually describes downloadable schemas or manifests |
| contact page | ContactPage and Person | visible contact/about content matches structured fields |
Blocked use
The site must not use structured data to claim certification, endorsement, live tool execution, hidden credentials, safety proof, ranking performance, or any fact that the visible page does not support.