Repository navigation
docs: add RFC for the Crewmates launch - #12813
Conversation
|
Intent: Put the CrewMates launch decisions (vocabulary, screens 01-09, out of scope) on main as an accepted RFC, so the launch PRs cite a recorded decision instead of proposing one. |
GPT 5.6 Review — ✅ no blocking findingsGPT 5.6 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Opus 4.8 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Design Review (Fable 5) — ✅ PASSDesign-level review of Design-Verdict: PASS Merging is the acceptance act for all nine screens at once — the maintainer should consciously ratify the born- [DESIGN-REVIEWED] e710d41 |
2116aa5 to
8fcade9
Compare
GPT 5.6 Review —
|
1 similar comment
GPT 5.6 Review —
|
8fcade9 to
ab14ad4
Compare
|
Inherited CI red on
This PR changes two Markdown files under |
ab14ad4 to
d4db7b5
Compare
d4db7b5 to
e710d41
Compare
Problem / Motivation
The CrewMates launch changes what a person sees: the "Agent Capabilities" page becomes Customize, the crewmate panel's "Crew summary" tab is replaced by Notes / Work log / Dashboard, a crewmate's chat shows only what it says to you, and crewmates can be grouped into teams. Nothing under
docs/request-for-change/records any of it. The First Principles lane has already blocked #12805 and #12806 for exactly that: "product-shape change without accepted RFC".Why it matters
Every launch PR replaces or removes something a person can see today. Under the RFC README's status vocabulary, that kind of change must trace to an
accepteddocument on the base branch. Without one, each of the eight launch PRs needs its own maintainer override, and the reasoning behind the launch lives only in a review nobody in the repository can read.What changed (motivation → approach → change)
One new document,
docs/request-for-change/rfc-crewmates-launch.md, statusaccepted, recording the product owner's review of 2026-09-22. It fixes the vocabulary (crewmate, custom agent, Built from, chat, thread, team, Customize; "agent" is no longer a top-level word), states the positioning line, and records screens 01 to 09 as decisions: the Customize page and its two tabs, the empty state and New crewmate dialog, the one-time opt-in for existing custom agents with the most recently used chat opening by default, the detail page as the one place to configure, the chat that shows only what the crewmate says with the bubble corner rule, the three-tab panel with Crew summary removed, reply threads, the four-step Meet CrewMates flow, and teams with the grouped roster and team view. It names what is out of scope, the acceptance conditions, the four open PRs and the five branches still to open.The RFC index in
docs/request-for-change/README.mdgains the row and its audit sentence, both verified against87553ba866.Backwards compatibility
Compatible: documentation only; no code, route, key or string changes.
Tests
N/A — no code.
scripts/docs-lint.shpasses (the new document is indexed and every link resolves).Manual verification
scripts/docs-lint.sh,check_brand_name.py,check_changelog_history.py,check_comment_history.pyandcheck_feature_map.pyrun locally against the merge base; all pass. Grepped the document for internal identifiers, hostnames and paths: none.Related Issues
no linked issue: decision record for the CrewMates launch; the implementing PRs are #12797, #12798, #12805 and #12806.
Checklist
feat|fix|docs|refactor|perf|test|chore|ci|build|revert: ...)