docs: Composer on the front door; correct two claims the ecosystem outgrew - #3
Merged
Conversation
…tgrew The org profile is the first thing a visitor reads and it described a studio-only world: Composer — the product, hosted and running the governed pipeline in the browser since August — appeared nowhere, and two sentences were factually false. - dspack-studio's paragraph now leads with Composer (what it does, projects and portability, hosted vs local AI with the browser/agent boundary stated) and keeps the Studio as the replay exhibit it is. - Removed "The hosted demo replays the pipeline's receipts; it does not run the pipeline." The hosted app runs the deterministic gates, emission, and rendering in the browser; only the model turn leaves it. - The Next/Deferred list still named intent inference and the Astryx contract as not implemented. Both shipped — inference drives goal-first Build, and Astryx is a packaged first-class reference. Added the Composer milestone in their place. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the organization profile README to reflect the current product surface area and correct outdated claims from an ecosystem-wide documentation audit, ensuring the first-touch documentation matches how the pipeline and milestones actually work today.
Changes:
- Reframes the
dspack-studiodescription to lead with Composer and positions Studio as the hosted replay exhibit. - Corrects the hosted-app claim to state the deterministic pipeline (gates, emission, rendering) runs in-browser, with only the model turn leaving the client.
- Updates the milestones by adding the Composer (Aug 2026) milestone and removing items that are no longer deferred (intent inference, full Astryx contract).
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Found during an ecosystem-wide documentation audit. The org profile README is the first thing anyone reads, and it still described a studio-only world.
No other section touched; the ecosystem repo descriptions, M1–M3 milestones, and evidence links were verified accurate and left alone.
🤖 Generated with Claude Code