Publication IntegrityDemonstratedv1.10.0
Evidence and Provenance
Evidence levelDemonstrated
Cognivirus.com uses six evidence labels, local source summaries, /docs/manifest.json, /docs/integrity-manifest.json, and UTC review dates to keep research-dependent claims inspectable.
Direct answer
Every major Cognivirus claim should show what kind of evidence supports it, where the supporting source summary lives, what the evidence does not show, and when the item was reviewed. The site must distinguish primary findings from site interpretation.
Evidence labels used by the site
- Demonstrated
- Experimentally observed
- Emerging evidence
- Architectural inference
- Open research question
- Speculative scenario
Provenance surfaces
| Surface | Purpose |
|---|---|
/docs/manifest.json | Lists source metadata, evidence level, publication date, and local summary path. |
/docs/integrity-manifest.json | Records SHA-256 hashes for preserved local docs and summaries. |
/evidence | Provides readable claim cards and source summaries. |
.uai/long-term-memory.uai | Points future maintainers to durable reports, summaries, and handoff records. |
/contact | Gives a human correction path. |
Limitation
A hash proves that a local file did not silently change after hashing. It does not prove that an external source is true, complete, current, or universally applicable.