From 52627400c0a0f7c1b202d47668e57e1cb2e56840 Mon Sep 17 00:00:00 2001 From: Ryan Dombrowski Date: Wed, 5 Aug 2026 10:46:02 -0400 Subject: [PATCH] =?UTF-8?q?docs(readme):=20describe=20the=20composer=20as?= =?UTF-8?q?=20shipped=20=E2=80=94=20Build,=20Catalog,=20Scenarios?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The README described only the exhibit; the composer and its Build workflow shipped without a word at the top level. This adds the verified framing and nothing beyond it: - Build creates governed interfaces through conversation from the project's APPROVED components, streaming gates/repair/emit per turn, rendering through the trusted registry, refining conversationally, and accepting results as governed worked examples; - Catalog is where a team teaches Studio what may be built; - Scenarios remains hand-authoring of governed examples; - the full Build workflow requires the local agent, named with its exact command, and the hosted composer says so plainly; - the hosted composer runs no hosted AI and uploads no project source, with `scripted` needing no model at all; - creating components a catalog lacks is future Component Workshop work — chat never generates component implementations. Additive only: the existing exhibit documentation is untouched, and no claim exceeds the released vertical slice. Co-Authored-By: Claude Opus 5 --- README.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/README.md b/README.md index 137fc88..def5778 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,28 @@ a recipe co-editor with real ingredients and instructions, Break-it Mode inspectors. See [docs/AUDIT.md](docs/AUDIT.md) for the plan-vs-implementation map. +**The composer** ([composer.aesthetic-function.com](https://composer.aesthetic-function.com)) +is the second surface in this repository: where a team sets up its own design +system and then builds with it. + +- **Build** — create governed interfaces through conversation, from the + project's approved components only. Each turn streams its generation, + S1–S3 gates, bounded repair, and emit result; renders through the project's + trusted registry; refines conversationally; and can be accepted as a + governed worked example. **The full Build workflow requires the local + agent** (`pnpm --filter agent dev`) — the hosted composer shows the demo + project's Catalog side and says so plainly. +- **Catalog** — connect a project, discover and enrich its contract, map it + to A2UI, author governance, track ownership, and validate. This is where a + team teaches Studio what may be built. +- **Scenarios** — author and inspect governed worked examples by hand. + +The hosted composer runs **no hosted AI and uploads no project source**: +generation happens on your machine through the local agent, against models +you choose (a deterministic `scripted` mode needs no model at all). Creating +components that a catalog does not yet contain is future **Component +Workshop** work — chat never generates component implementations. + ## Try it ```sh