docs: add XZBT project page and initial development log

2026-09-04 20:32:33 -07:00
parent 7b2e486095
commit ca2830174f
7 changed files with 274 additions and 0 deletions
@@ -0,0 +1,33 @@
+# Instructions for the Labyricorn project record
+
+These instructions supplement `.labyricorn/AGENTS.md` and apply to the
+`project/` directory.
+
+## Record structure
+
+- Maintain exactly one project record at `project/contents.lr` using
+  `_model: project` and `schema_version: 1`.
+- Keep `project_id` stable. It is the durable identity used by the importer and
+  public URL.
+- Ask before changing the repository URL, default branch, project status,
+  author, start date, or project identity.
+- Store project-owned images in this directory and reference them by filename
+  from `contents.lr`. Only PNG, JPEG, and WebP images are accepted.
+
+## Editorial guidance
+
+- Write the exhibition page as a concise project narrative, not as a copy of
+  the repository README or as release documentation.
+- Verify technical and status claims against the repository before editing.
+- Distinguish completed work, formal design work, experiments, and future work.
+- Do not manually add repository-derived commit, license, language, release,
+  issue, star, or fork metadata. The Labyricorn importer owns those values.
+- Keep the summary suitable for listings and social previews.
+
+## Review requirements
+
+- Confirm all required project fields are present and any image reference stays
+  inside `project/`.
+- Check Markdown links are intentional HTTPS links and prose makes no unsupported
+  claims.
+- Validate the record and run `git diff --check` before committing.
@@ -0,0 +1,35 @@
+_model: project
+---
+schema_version: 1
+---
+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.
+---
+status: active
+---
+started: 2026-09-04
+---
+author: Labyricorn
+---
+repository_url: https://git.labyricorn.com/Labyricorn/XZBT
+---
+default_branch: main
+---
+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.
+
+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](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.