← Instrument galleryD19-SPATIAL-HOME-PROJECTION-LAB

Spatial Home Projection Lab

A deterministic browser-local research instrument.

DETERMINISTIC FIXTURE · NOT A PERFORMANCE RESULT

Spatial Home Projection Lab

MECHANISMMeaningful spatial projections over shared project state
AUTHORITYProject Core, voluntary sharing, and threshold leases
COMMIT RULEStateIntent and bounded crossing precede consequential work.
FAIL-CLOSED RULEUnavailable work stays unavailable; no fake ambient activity.
STATEPRIVATEc0b5ce1b
projection0
threshold scopePRIVATE
Return receiptc0b5ce1b
  1. PRIVATE
  2. PUBLIC_SELECTED
  3. AVAILABLE_BOUNDED
  4. STATE_INTENT
  5. RETURNED
  6. RECEIPTED
  7. UNAVAILABLE
CONTRACT CONTROLS

Each control executes a declared browser-local transition. Repeated dual-outcome controls alternate deterministically.

FIXTURE ASSERTIONS

NOT YET EXERCISEDEvery projection resolves to the same objects and events.

NOT YET EXERCISEDNo ambient motion occurs without event state.

NOT YET EXERCISEDCrossing a threshold exposes scope and revocation.

NOT YET EXERCISEDUnavailable Station is truthful rather than animated as working.

RECEIPTED EVENT LOG

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

Compare Architectural Home, radial, Workfield, Corolla, and list projections over identical Project state.

Mechanism

The same events and objects render in multiple projections. Place selections emit StateIntent, threshold crossings disclose grants, and ambient changes require real events.

Deterministic fixture

A resident Home with Door, Porch, Desk, Workshop, three projects, two Returns, one visitor request, and one unavailable Station.

The fixture must live in content/demos/d19-spatial-home-projection-lab/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

  • Switch projection
  • Select Desk
  • Declare Porch
  • Open Door preview
  • Review visitor request
  • Dispatch Station
  • Emit Return
  • Verify Receipt
  • Toggle reduced motion/list mode

Visible states

  • PRIVATE
  • PUBLIC_SELECTED
  • AVAILABLE_BOUNDED
  • STATE_INTENT
  • RETURNED
  • RECEIPTED
  • UNAVAILABLE

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

  1. Every projection resolves to the same objects and events.
  2. No ambient motion occurs without event state.
  3. Crossing a threshold exposes scope and revocation.
  4. Unavailable Station is truthful rather than animated as working.

Layout

The page contains:

  1. a concise mechanism explanation;
  2. the interactive stage;
  3. a state and evidence inspector;
  4. a reset control;
  5. a “what this proves / what it does not prove” panel;
  6. 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

Behavioral superiority of any projection remains an empirical question.

The interface must never convert illustrative values into a benchmark claim. A measured result appears only when linked to a versioned run receipt.