← Instrument galleryD08-TEMPORAL-ATLAS

Temporal Atlas / Video Address Map

A deterministic browser-local research instrument.

DETERMINISTIC FIXTURE · NOT A PERFORMANCE RESULT

Temporal Atlas / Video Address Map

MECHANISMStable temporal identity over exact media intervals and branches
AUTHORITYExact segment identities and lineage graph
COMMIT RULEReplacement supersedes a representation without rewriting logical scene identity.
FAIL-CLOSED RULEBranches retain parent history and exact source evidence.
STATECANONa66f0969
scene identity0
source intervalCANON
branch lineagea66f0969
  1. CANON
  2. BRANCH
  3. SUPERSEDED
  4. PERSISTENT_OBJECT
  5. EXACT_SEGMENT
  6. GENERATED_REPRESENTATION
CONTRACT CONTROLS

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

FIXTURE ASSERTIONS

NOT YET EXERCISEDLogical scene identity survives a shot replacement.

NOT YET EXERCISEDExact source range remains independently addressable.

NOT YET EXERCISEDBranch edits do not rewrite the parent timeline.

NOT YET EXERCISEDContinuity constraints are visible and testable.

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

Navigate video by stable scenes, events, objects, shots, branches, and exact segments rather than only timestamps.

Mechanism

A temporal object graph links logical identities to exact source ranges, revisions, branches, continuity constraints, and representation routes. Address-stable edits target objects and invariants.

Deterministic fixture

A ninety-second fictional sequence with six scenes, three persistent characters, two branch edits, and one replaced shot.

The fixture must live in content/demos/d08-temporal-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

  • Scrub time
  • Select scene/event/object
  • Follow lineage
  • Switch branch
  • Replace shot
  • Preserve invariant
  • Open exact segment
  • Show representation route

Visible states

  • CANON
  • BRANCH
  • SUPERSEDED
  • PERSISTENT_OBJECT
  • EXACT_SEGMENT
  • GENERATED_REPRESENTATION

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. Logical scene identity survives a shot replacement.
  2. Exact source range remains independently addressable.
  3. Branch edits do not rewrite the parent timeline.
  4. Continuity constraints are visible and testable.

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 fixture demonstrates the address model, not a new production video codec result.

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