ReferenceDemonstratedv1.10.0

Liquid Layout and Interface Map

EvidenceDemonstrated

This page records the v1.6.0 interface rule: Cognivirus.com should behave like a research observatory, not a narrow static memo. The layout should use the whole available viewport while preserving readable line lengths for prose.

animated flowchart · transition graph

The unsafe unit can be the transition graph.

The relevant safety boundary includes every permitted transformation, not only the current model artifact.

01Fine-tunenew local behavior
02Attach LoRAsmall deltas carry strategy
03Mergecapabilities recombine
04Routecapability appears only on path
05Evaluatemetric becomes selection
06Promotealias changes identity
07Persistmemory and descendants retain residue
08Rollbackmust restore ecology, not one file
schematic · liquid screen use

Use the viewport as a systems map.

Wide screens should carry the transition graph, source context, contact/accountability, and version state. Prose stays readable; the system view expands.

bounded prosereadable measure expanded diagrams · tables · tools sticky railcontact · version · graph

Liquid layout targets

TargetImplementation
Wide canvasUse a nearly full-width shell on desktop displays.
Readable proseKeep paragraphs bounded while diagrams, tables, cards, and tools expand.
Persistent side railKeep transition-graph context, contact/accountability, and high-value paths visible.
Versioned surfacesShow release numbers in the header, page metadata, footer, and machine-readable files.

Rules

What changed in v1.6.0

v1.7.0 deep schematic extension

The liquid layout now reserves extra width for detailed interactive schematics with node-level explanations. Wide screens should show both the prose argument and the relevant transition, manifest, evaluator, rollback, or memory map.

See Deep Schematic System Map.