Skip to content

docs(rfc): rename the Mate to the Jam (full name Crew Jam), with the export file and reports folder - #26490

Closed
iamwhatever wants to merge 1 commit into
mainfrom
docs/rfc-crew-jams-rename
Closed

iamwhatever wants to merge 1 commit into
mainfrom
docs/rfc-crew-jams-rename

Conversation

@iamwhatever

@iamwhatever iamwhatever commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Record the owner's decision to rename the Mate to the Jam (plural Jams; full name Crewmate becomes Crew Jam), with the export file and the reports folder, so later waves can be checked against one list.

The owner decided on 2026-10-30 that the standing teammate agent's short name Mate / Mates becomes Jam / Jams (the Mates page becomes the Jams page) and its full name Crewmate becomes Crew Jam, untranslated in every language. The export file and the reports folder are names a person sees too, so they move with it. Old .crewmate files keep importing.

Why it matters

The rename touches every catalog, the export reader and a folder people already have. Without one written list of what changes and what stays, each wave would draw its own line, and a reviewer could not check it.

Not a goal

  • No code change. Implementation is waves W0b to W4 in §8.
  • No rename of code symbols, i18n keys, API fields, config keys, routes, card kinds or MCP names (§3.4).
  • No edit to any docs/decisions/ entry. The superseding entry is its own PR (W0b), as docs/decisions/README.md rule 3 requires.

What changed (motivation → approach → change)

File Change
docs/request-for-change/rfc-crew-jams-rename.md new RFC, status: accepted
docs/request-for-change/README.md index row and audit note

The RFC records:

  • §3.1 the words: Jam / Jams for every Mate / Mates, Crew Jam only where the full name was used; brand-like, on the do-not-translate list; the seeded crewmate keeps its name "Mate".
  • §3.2 export writes only .crewjam / crewjam.json / kirocrew.crewjam; import reads both forms under the same checks.
  • §3.3 reports move to Jams/<name>/Reports with a one-time rename-or-merge migration, metadata only.
  • §3.4 the identifiers that stay.
  • §4 a scope inventory measured at fea0920bf8, with the commands that reproduce it.
  • §5 the correctness rule each wave is checked against, and §8 the wave plan.

Backwards compatibility

Compatible: docs only.

Removes nothing: no code, key or path changes in this PR.

Tests

Docs only. scripts/docs-lint.sh passes. scripts/check_brand_name.py passes on the changed files.

Manual verification

N/A — docs-only change.

Related Issues

Refs #20965

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@github-actions

github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ⏭️ skipped

Revision 822d492b079076d2b31c3da49ee23f0f9b7e82d8 ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Does not block merge.

@github-actions

github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 822d492b079076d2b31c3da49ee23f0f9b7e82d8 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 31, 2026
@github-actions

github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 822d492b079076d2b31c3da49ee23f0f9b7e82d8 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

This PR only adds docs. It writes down an owner decision, lists what stays the same, and includes compatibility and downgrade plans.

Notes

  • §3.3 runs the migration once per install, using a marker. After a downgrade and then an upgrade, reports stay split between Crewmates/ and Jams/. Running the migration whenever a top-level Crewmates folder exists, with no marker, would avoid that. It would also stay idempotent.

[DESIGN-REVIEWED] 822d492

Description read

[DESCRIPTION-READ] 0fdfc5a477c6cc2ae7a35bf8c7827f9e758fc931935676a517bd35d82788d844

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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 822d492b079076d2b31c3da49ee23f0f9b7e82d8 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 822d492

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 822d492b079076d2b31c3da49ee23f0f9b7e82d8 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 822d492b079076d2b31c3da49ee23f0f9b7e82d8 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 822d492

Verdict parsed from the review's SHA-scoped output markers for commit 822d492b079076d2b31c3da49ee23f0f9b7e82d8.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 822d492b079076d2b31c3da49ee23f0f9b7e82d8 false-positive: <reason, 20 to 500 characters>

@iamwhatever
iamwhatever force-pushed the docs/rfc-crew-jams-rename branch from 75c6394 to aea54a9 Compare October 31, 2026 00:58
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 31, 2026
@iamwhatever
iamwhatever force-pushed the docs/rfc-crew-jams-rename branch from aea54a9 to 20af711 Compare October 31, 2026 04:57
iamwhatever pushed a commit that referenced this pull request Oct 31, 2026
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.
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision labels Oct 31, 2026
@iamwhatever iamwhatever changed the title docs(rfc): rename the Mate to the Crew Jam, with the export file and reports folder docs(rfc): rename the Mate to the Jam (full name Crew Jam), with the export file and reports folder Oct 31, 2026
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 31, 2026
@iamwhatever
iamwhatever force-pushed the docs/rfc-crew-jams-rename branch from 20af711 to 822d492 Compare October 31, 2026 05:22
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 31, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Closing as superseded by #26452, which already renames Mate to Jam. The maintainer decided to keep the .crewmate extension and the Crewmates/ reports folder for backward compatibility, so this RFC is no longer needed.

@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant