XZBT

XZBT is being built around a simple distinction: the runtime knows how; the exhibit defines what. A self-contained XZBT.html will interpret declarative .xzbt JSON exhibits to create procedural visuals, soundscapes, and evolving audiovisual performances without exhibit-authored JavaScript.

The intended experience is to open the HTML directly in a desktop Chromium browser, import exhibits, and run them offline. Parameters, state, audio and visual primitives, events, cadence, and scenarios will provide reusable building blocks for very different exhibits. The engine is intended to stay independent of any particular theme.

The MVP requirements and seven gap-closure decisions are documented. Implementation currently consists of a disposable Phase 0 feasibility probe and two minimal fixtures, Amber Study and Blue Study. This is an experiment in browser capabilities, not the production runtime or a completed MVP.

Manual Chrome testing has demonstrated ordinary import, exhibit selection, saved settings restored after a browser restart, native audio, embedded data-URL AudioWorklet loading, offline operation, and continued session operation during injected storage failures. Renamed and relocated copies also restored data in the tested environment; that behavior is not a general browser compatibility guarantee.

Development is stalled in Phase 0 at the GC1 feasibility gate. Directory-permission-denial or API-unavailability fallback remains unverified. Shared format contracts, semantic traces, and milestone preparation are also unfinished. Phase 1 and every subsequent implementation phase have not started. Performance benchmarks and the required development and release soaks remain future work.

The project repository contains the product requirements and planning baseline. The initial development log links the planning baseline and the subsequent probe and manual-evidence commit separately.