Labyricorn/XZBT
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(labyricorn): update project page description and phase status

Browse Source
This commit is contained in:
Labyricorn
2026-09-05 15:11:45 -07:00
parent 7812d70557
commit cc36878a0f
1 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.labyricorn/project/contents.lr
+9 -7
View File
@@ -6,7 +6,7 @@ project_id: xzbt
---
title: XZBT
---
summary: A planned single-file browser runtime for declarative procedural visuals and soundscapes. Development is stalled in Phase 0 feasibility and contract preparation.
summary: A standalone browser runtime for declarative procedural visuals and soundscapes, now implemented through the Phase 2 common grammar milestone.
---
status: active
---
@@ -22,14 +22,16 @@ tags: Generative Art, Procedural Audio, Browser Applications
---
body:
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.
XZBT is being built around a simple distinction: the runtime knows how; the exhibit defines what. A self-contained `XZBT.html` interprets declarative `.xzbt` JSON exhibits without allowing exhibit-authored JavaScript. Later engine phases will build procedural visuals, soundscapes, and evolving audiovisual performances on that generic foundation.
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 intended experience is to open the HTML directly in a desktop Chromium browser, import exhibits, and run them offline. The production runtime now provides the application shell, exhibit library, validation and diagnostics, controlled activation and teardown, deterministic seeded random streams, IndexedDB caching, and session-only fallback when storage is unavailable.
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.
Phase 2 adds the shared declarative grammar: typed user parameters, simulation state, read-only runtime signals, ValueSpec and ConditionSpec evaluation, same-tick bindings, ordered state actions, numeric transitions, and temporary overrides that preserve underlying user configuration. Two small subject-neutral exhibits exercise this runtime without embedding subject-specific behavior in `XZBT.html`.
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.
Phase 0 is complete. Its browser feasibility work demonstrated ordinary import, exhibit selection, restart restoration, native audio, embedded data-URL AudioWorklet loading, offline operation, storage-failure fallback, and directory-picker fallback in the tested Chrome environment. Its shared format, resolution, clock and reproducibility, and ownership and failure contracts are backed by deterministic tests.
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.
Development is active after completing the Phase 1 runtime skeleton and Phase 2 common grammar. Their automated production suites and the unchanged GC2 through GC5 contract oracles pass. The production artifact's user-observed direct-file two-exhibit import and full-browser restart check remains open; this is a recorded acceptance observation, not a Phase 0 implementation stall.
The [project repository](https://git.labyricorn.com/Labyricorn/XZBT) contains the product requirements and planning baseline. The initial development log links the planning baseline and the subsequent probe and manual-evidence commit separately.
Audio synthesis, visual rendering, cadence and events, scenario direction, the final generated UI, library hardening, reference exhibits, performance benchmarks, and the required development and release soaks remain future phases. XZBT is therefore an implemented runtime foundation, not yet a completed 0.1 MVP.
The [project repository](https://git.labyricorn.com/Labyricorn/XZBT) contains the product requirements, standalone artifact, source modules, exhibits, tests, implementation status, and verification evidence. The development log records the Phase 0 contracts and the combined Phase 1–2 runtime milestone.