Repository navigation
docs(decisions): the standing teammate agent is called a Crew Jam - #26503
iamwhatever wants to merge 1 commit into
Conversation
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS This is a docs-only decision record that supersedes the old entry as rule 3 requires; it removes nothing and adds no rendered surface. Notes
[DESIGN-REVIEWED] 4d73134 Description read[DESCRIPTION-READ] 45aab57870ee449707eea3f53558ae4ec6a37b17844cde0f0004d74d4f770cfd That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — 🔴 changes requested (blocking)Reviewed Blocks under BLOCKING — docs/decisions/2026-10-31-the-standing-teammate-agent-is-called-a-crew-jam.md:5 [BLOCK-MERGE] 4d73134 Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — 🔴 changes requested (blocking)GPT 6.1 found at least one blocking issue that must be resolved before merging This comment is updated in place on each push. BLOCKING -- docs/decisions/2026-10-31-the-standing-teammate-agent-is-called-a-crew-jam.md:5 -- Superseding a recorded decision requires maintainer override
[BLOCK-MERGE] 4d73134 Adjudication (Opus 5.5) — is blocking on each finding proportionate?The rule flags every superseding entry on purpose ( 🏷️ Fenced finding(s) machine-flagged as likely edge caseThe security fence keeps these findings blocking regardless of adjudication; the only clearance path is a human override. The annotate-only pass judged the condition combination each one requires extreme, and pre-drafted the override rationale below. A repository writer must independently verify a rationale before posting it — it is machine-authored, and a wrong override on a security-class finding ships exactly the class the fence exists to stop.
Replace False positive or not applicable? A repository writer can comment: |
Adds a superseding decision entry for 2026-10-15-the-standing-teammate-agent-is-called-a-mate.md: full name Crew Jam, short UI name Jam (plural Jams), untranslated in every catalog; the export file becomes .crewjam and the reports folder Jams/. Decided by maintainer Joe Guo (@iamwhatever). Docs only. Refs #26490.
3a723be to
4d73134
Compare
|
Closing as superseded by #26452, which carries its own decision entry superseding the 2026-10-15 Mate entry. No override was posted here. |
Problem / Motivation
Goal: Add the decision entry that supersedes
docs/decisions/2026-10-15-the-standing-teammate-agent-is-called-a-mate.md, so the Crew Jam rename planned in RFC #26490 is a recorded decision.Maintainer Joe Guo (@iamwhatever) decided on 2026-10-31 that the standing teammate agent's full name is Crew Jam (where "Crewmate" is used today) and its short UI name is Jam / Jams (where "Mate" / "Mates" is used today, e.g. the Jams page), untranslated in every catalog. In their words: "Crew mate有个新的名字 Crew Jams" and "Jams太难有中文名字了" (Jams is too hard to give a Chinese name).
Why it matters
docs/decisions/README.mdrule 3: a change of mind is a new entry with aSupersedes:line, in its own pull request. Until this entry lands, every wave of the rename would read as a regression of the 2026-10-15 entry.Not a goal
What changed (motivation → approach → change)
docs/decisions/2026-10-31-the-standing-teammate-agent-is-called-a-crew-jam.mdSupersedes: 2026-10-15-the-standing-teammate-agent-is-called-a-mate.mddocs/decisions/README.mdThe entry records: full name Crew Jam, short name Jam / Jams; no translation in any catalog (zh-CN replaces 队友 with Jam / Jams); export writes
.crewjam/kirocrew.crewjam/crewjam.jsonand import still reads the old form; reports move toJams/{name}/Reportswith a one-time migration; code identifiers, i18n keys, API paths, config keys, routes and persistedcrewmate_*state are unchanged.Backwards compatibility
Compatible: docs only.
Removes nothing: the old entry is kept unchanged, as rule 2 requires.
Tests
Docs only.
DECISIONS_BASE_REF=origin/main python3 scripts/check_decisions_history.pypasses (37 entries intact).scripts/docs-lint.shpasses.scripts/check_brand_name.pypasses on the changed files.Manual verification
N/A — docs-only change.
Expected review result
The
recorded-decisions-are-not-regressionsrule flags this PR by design (rule 3). A maintainer override is what lets it land.Related Issues
Refs #26490
Refs #20965
Checklist