LABSPUBLIC RESEARCH INSTITUTE
← Instrument galleryD02-FOVEA-ADDRESS-ATLAS

FOVEA Address Atlas

A deterministic browser-local research instrument.

Related paperBenchmark contract
DETERMINISTIC FIXTURE · NOT A PERFORMANCE RESULT

FOVEA Address Atlas

MECHANISMQuadkey address fabric with evidence-bound LOOK
AUTHORITYExact object identity outside the atlas
COMMIT RULEA trusted rim requires a matching placement receipt.
FAIL-CLOSED RULECorrupt or unreceipted content renders a proof breach.
STATEEXACT_LOCAL0323430d
quadkey depth0
logical frameEXACT_LOCAL
proof rim0323430d
  1. EXACT_LOCAL
  2. SUMMARY
  3. GLYPH_ONLY
  4. UNLOADED
  5. PROOF_OK
  6. PROOF_BREACH
CONTRACT CONTROLS

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

FIXTURE ASSERTIONS

NOT YET EXERCISEDParent/child/neighbor operations match golden vectors.

NOT YET EXERCISEDThe same LookState produces the same logical frame.

NOT YET EXERCISEDSpatialAddress never changes ContentId or logical identity.

NOT YET EXERCISEDAn unreceipted fold cannot display the trusted rim.

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

Make stable quadkey place, Hilbert order, exact neighborhood math, foveation rings, landmarks, and proof-bound unfold visible.

Mechanism

A recursively subdivided field assigns base-4 quadkeys. Hilbert order is shown as a derived storage traversal. The reticle creates foveal, parafoveal, peripheral, and unloaded budgets. Proof state controls whether content may unfold as trusted.

Deterministic fixture

A depth-six atlas containing accepted, disputed, stale, and unreceipted objects with deterministic seed-based landmark skins.

The fixture must live in content/demos/d02-fovea-address-atlas/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

  • Zoom in/out
  • Move reticle
  • Enter quadkey
  • Toggle Hilbert path
  • Toggle landmarks
  • Change ring budgets
  • Corrupt proof
  • Restore LOOK state
  • Compare plain grid

Visible states

  • EXACT_LOCAL
  • SUMMARY
  • GLYPH_ONLY
  • UNLOADED
  • PROOF_OK
  • PROOF_BREACH

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. Parent/child/neighbor operations match golden vectors.
  2. The same LookState produces the same logical frame.
  3. SpatialAddress never changes ContentId or logical identity.
  4. An unreceipted fold cannot display the trusted rim.

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

The demo proves address and view mechanics. It does not prove that landmarks improve memory or that foveation beats modern lazy loading.

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