Interactive Schematics
Cognivirus.com should not read like a static memo. The site explains transition graphs, adapter ecologies, evaluator gates, assurance decay, and rollback completeness, so the interface should let visitors see those systems moving.
This page records the visual design rule added during the UI/UX improvement round: the site should remain visually active and interactive without becoming sensational. Motion is used to clarify flow, persistence, transition, and stale assurance. It is not used as fake telemetry, fear imagery, or proof that any system is alive.
Core schematic motifs
The diagram shows a bounded evolutionary loop. Feed supplies evidence and resources. Fork creates candidates. Fight evaluates candidates. Flee removes unsafe or wasteful states. No-op is shown at the center to preserve non-growth as a legitimate outcome.
Adapter reproduction is a boundary, not a feature toggle.
Select a phase to inspect how a small adapter delta can become a system-level persistence problem when composition, evaluation, and memory reinforce it.
Individually acceptable adapters may create an untested state when loaded together, especially when load order, merge coefficients, quantization, and prompt policy change.
The evaluator does not need to be malicious. If its score has a loophole, repeated candidate generation can preserve whatever exploits that loophole.
Memory, synthetic training examples, descendants, registry aliases, and routing statistics can retain the pattern after the first adapter is retired.
Ecological rollback must include base weights, adapters, router, prompt policy, memory snapshot, evaluator version, permissions, aliases, and external effects.
The control plane is both guardrail and target.
External governance is necessary for adaptive ecologies. It also concentrates authority in the evaluator, registry, router, release controller, hidden tests, signing keys, and rollback machinery.
plane hidden testsevaluatorregistrysigning keysrouterrollbackhuman approvalmemory policy
Evidence decays when the evaluated state stops being the deployed state.
The worksheet logic is visualized as an evidence half-life: every material change pushes some previous claim from current, to review-needed, to stale, to unknown.
The package memory points to the evidence, not around it.
AGENTS.md points the receiver into .uai. Long-term memory points into /docs. Source reports remain preserved as reports, while .uai records what was used, where, and why.
Interaction rules
Visitors may hover, focus, or tap flow nodes to inspect a stage. Every animated schematic has a text equivalent. The site respects reduced-motion settings. Diagrams must not include literal pathogens, skulls, humanoid robot heads, fake terminal feeds, or unsupported live-status claims.
UX standard
A page about a dynamic ecology should expose at least one of these surfaces when practical: a topology diagram, a flowchart, a manifest view, a schematic rail, an evidence card, a worksheet, or an interactive atlas. The goal is to make relationships visible before adding more prose.
Detailed v1.7.0 schematic set
The v1.7.0 visual round adds deeper inspection layers. Visitors can now focus or tap individual nodes to see why a stage matters. These diagrams are explanatory schematics, not live telemetry and not operational replication instructions.
The teleodynamic loop separates sensing, resource intake, candidate generation, evaluation, retirement, and no-op. The budget gate prevents growth from becoming its own objective.
The flow shows a non-operational governance boundary: adapter variants are identified, verified, composed, evaluated, canaried, selected, and later reviewed for behavioral extinction.
Who evaluates the evaluator is a systems question.
This schematic expands the control plane into separable assets: policy owners, hidden tests, deterministic validators, model judges, evidence stores, signing keys, promotion rules, and disagreement monitors.
Retirement removes a carrier, not every reservoir.
Behavioral residue can remain in memory, examples, evaluator expectations, routing statistics, human procedures, and descendant training material.
A rollback packet must restore the ecology.
A model-weight rollback is incomplete when behavior depends on adapters, memory, router aliases, evaluator versions, permissions, and external side effects.
Reports live in /docs; memory points from .uai.
The package treats raw source reports and public summaries as evidence objects, while .uai files carry durable project memory, release state, handoff instructions, and pointer ledgers.
read first .uai/index.uai
map.uai/totem.uai
principles.uai/release.uai
version state.uai/long-term-memory.uai
pointers/docs/source-reports
preserved reports/docs/source-report-summaries
public-safe synthesis/content
published pages/tests
validation