docs(readme): describe the composer as shipped — Build, Catalog, Scenarios - #46
Merged
Conversation
…arios 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 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the top-level README to describe the composer surface that ships with the repository (Build, Catalog, Scenarios), clarifying what is hosted vs what requires the local agent and how generation is governed.
Changes:
- Add a new README section introducing the hosted composer and its role as the second surface in the repo.
- Summarize the responsibilities of Build, Catalog, and Scenarios, including S1–S3 gating and “approved components only”.
- Clarify operational boundaries: full Build requires the local agent command, and the hosted composer does not run hosted AI or upload project source.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| - **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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README documented only the exhibit; the composer and its Build workflow shipped without a top-level mention. This adds the verified framing — additive only, existing exhibit copy untouched, no claim beyond the released slice.
Covers exactly the agreed points:
pnpm --filter agent dev), and the hosted composer says so plainly.scriptedneeds no model at all.One file, +22 lines. Ships with the Phase 3 production release.
🤖 Generated with Claude Code