DR-35: align the profile with the amended CANON §3 - #4
Merged
Conversation
af-site's CANON.md was amended on 2026-08-12 to govern Composer's maturity language directly, and CANON's preamble binds this README as a governed surface. The amendment makes this file the OVERSTATING one, so it moves in the same governed event rather than drifting the other way. "is the product" becomes the §3 wording: the flagship experience of the open ecosystem and the clearest demonstration of governed AI interface generation. §3 refuses "the product" as a description of Composer on any surface, because Composer is in active testing and presenting it as a finished commercial offering would not be true yet. A paragraph states the maturity and the present limits in the same place Composer is introduced, which §3 requires wherever it is introduced at length. dspack-studio "is the flagship" becomes "carries the ecosystem's two hosted surfaces", matching the amended §5 classification: the flagship is the Composer experience, and the repository is what carries it and the Studio. No em-dashes added. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the organization profile README to align Composer and dspack-studio language with the amended CANON §3 maturity/flagship terminology, avoiding overstating Composer’s status while keeping existing factual claims intact.
Changes:
- Reframes dspack-studio from “the flagship” to the repository that carries the two hosted surfaces.
- Rewords Composer’s introduction to “flagship experience” (not “the product”) and adds an explicit maturity/limitations paragraph.
- Adjusts the August 2026 milestone wording to reflect “active testing” rather than “became a product”.
💡 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.
CANON.md in
af-sitewas amended on 2026-08-12 (DR-35) to govern Composer's maturity language directly. CANON's preamble binds this README as a governed surface, and the amendment makes this file the overstating one, so it moves in the same governed event rather than drifting the other way.The drift that opened the whole investigation was canon falling behind this README. This PR is the other half: keeping them from diverging in the opposite direction.
What changes
No em-dashes added. Every factual claim (browser-side pipeline execution, provider options, renderer coverage) is unchanged.
🤖 Generated with Claude Code