Guide / Instrument Precision

How to extend this surface without breaking the proof system.

What this pattern assumes.

Engineering language is not a brand style choice. It should fit the project: tight rails, explicit labels, measurement hints, and no invented claims. Trust comes from declared uncertainty, not visual hype.

When to add variation.

Change should be bounded: add a proof tier when there is a new verification class, expose a measurement mode when layout scale becomes the story, and leave the grid alone if the content still fits.

Proof tier system.

Use these labels exactly. Expand only when a new status class is provably different.

RealVerified build, live systems, documented clients.

ConceptFiction labeled fiction. Simulated context, unbuilt proposal.

DemoInterface exists, but lacks client contract or live data.

Inspector mode.

Enable measurement visibility when layout scale or alignment is the value being sold. Disable in reduced-motion environments. Hide on mobile below 720px.

Toggle through the Inspector button in the nav.
Escape exits inspector mode.
Resize and scroll update the measurement labels.
Use the cursor radius on desktop to read container dimensions.

Extension list.

Add assets/diagrams/*.svg when a structured diagram becomes the proof.
Update spec sheets under index.html when the project set changes.
Keep one H1 per document, no horizontal overflow, and a clean console.
Prefer inline SVG over external media for labels, measurements, and diagrams.