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.
Public UI Content Cleanup
Cognivirus.com removed public-facing text fragments that read like maintainer instructions rather than reader-facing explanation.
Direct answer
The public interface now explains the subject matter instead of describing how the interface should be built. Design and authoring notes were moved to internal maintainer files, while the visible rail and footer now speak to readers.
What changed
| Area | Public-facing repair | Internal destination |
|---|---|---|
| Live transition graphThe map of how an AI system is allowed to change over time. Open glossary definition rail | Now explains that the graph is a reader aid for understanding behavior movement across models, adapters, memory, evaluators, descendants, and rollbackReturning a system to an earlier known state. Open glossary definition paths. | .uai memory and maintainer notes |
| Layout card | Now presents reader exploration options instead of layout rules. | .uai design memory |
| Evidence card | Now explains how evidence labels help readers understand claim maturity. | .uai content memory and tests |
| Footer summary | Now describes the public research site rather than package structure. | release memory |
| Site-integrity page | Now uses public explanation headings rather than construction-language headings. | .uai handoff record |
Public-content rule
Public UI text should help visitors understand Cognivirus.com. Internal rules for maintainers belong in README, tests, comments, or .uai memory.
Why this matters
A research site loses credibility when it leaks build instructions into the reading experience. Cognivirus.com can still preserve strict internal writing rules, visual-design goals, and evidence discipline, but those rules should be invisible scaffolding unless the page is explicitly about site integrity.
Review boundary
This cleanup does not change the site's technical thesis, source reports, evidence labels, animated graph behavior, Risk Lab worksheets, or .uai report memory. It only removes internal implementation language from public chrome and article copy.