Truth Plane / Lens Plane
A deterministic browser-local research instrument.
217c37df- CANONICAL
- PROJECTED
- STALE
- BREACH
- CANDIDATE
- ACCEPTED
- REJECTED
Each control executes a declared browser-local transition. Repeated dual-outcome controls alternate deterministically.
NOT YET EXERCISEDDeleting all view state loses zero canonical events.
NOT YET EXERCISEDA stale projection is visibly labeled and cannot commit.
NOT YET EXERCISEDRejected candidate leaves the canonical head unchanged.
NOT YET EXERCISEDAccepted candidate appends an event and produces a receipt.
No transition yet. Operate a declared control.
This transparent browser-local instrument teaches the authored state contract. Exercising an assertion demonstrates fixture behavior only; it is not evidence of production performance, compression ratio, model uplift, cognition, safety, or universal correctness.
Purpose
Teach the separation between canonical LCSM state and reconstructable FOVEA or SurfaceMind projections.
Mechanism
A canonical event log drives two synchronized projections. Users may delete, reorder, filter, or corrupt a projection cache; the truth plane remains unchanged and can rebuild the view. A candidate mutation must pass the two-note review and authority gate before canon advances.
Deterministic fixture
A five-event project with one accepted decision, one superseded decision, one disputed claim, one artifact binding, and one stale projection cache.
The fixture must live in content/demos/d01-truth-plane-lens-plane/fixture.json, validate before the demo renders, and be resettable without a network call. A future live adapter may be added behind a visibly separate mode.
Required controls
- Select event
- Change projection lens
- Delete projection cache
- Inject stale view
- Propose mutation
- Accept or reject candidate
- Rebuild from journal
- Open receipt
Visible states
CANONICALPROJECTEDSTALEBREACHCANDIDATEACCEPTEDREJECTED
Every state must have text, iconography, and a non-color-only distinction. State transitions are logged in an in-memory demo receipt visible in the inspector.
Core assertions
- Deleting all view state loses zero canonical events.
- A stale projection is visibly labeled and cannot commit.
- Rejected candidate leaves the canonical head unchanged.
- Accepted candidate appends an event and produces a receipt.
Layout
The page contains:
- a concise mechanism explanation;
- the interactive stage;
- a state and evidence inspector;
- a reset control;
- a “what this proves / what it does not prove” panel;
- links to the related paper and benchmark contract.
On narrow screens the inspector becomes a bottom sheet. The stage must remain usable at 360 CSS pixels.
Accessibility
- All operations are keyboard reachable.
- Pointer gestures have button or keyboard equivalents.
- Animated transitions honor
prefers-reduced-motion. - Focus remains visible and returns predictably after sheets close.
- Diagrams expose concise text alternatives.
- Status is announced through a polite live region only when the user initiates the transition.
Instrumentation
Record locally:
demo_id
fixture_version
action
prior_state
result_state
validation_result
timestamp_relative
Do not send telemetry. Provide “Export demo trace” as JSON for debugging and reproducibility.
Automated tests
- fixture schema validation;
- deterministic reset;
- every required control transition;
- every assertion above;
- invalid and stale fixture handling;
- keyboard path;
- 360 px and 1440 px screenshots;
- zero critical console errors;
- no request to a paid API in default mode.
Publication boundary
This is a deterministic teaching implementation of the lane boundary, not a production LCSM deployment.
The interface must never convert illustrative values into a benchmark claim. A measured result appears only when linked to a versioned run receipt.