Repository navigation
docs: rfc for crewmate responsive send - #20889
Conversation
UX Review (Opus 5.5) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS The RFC is marked Watch
[DESIGN-REVIEWED] ea02e57 Description read[DESCRIPTION-READ] 2f15d652ce4acfabef18112154e364acf7f51fbc49c27d6ab9bc2fbbf6dfa231 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 — ✅ 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: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 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: |
Records the product owner's 2026-10-15 decision for crewmate DMs: a send to a busy crewmate steers first and cancels only after a 3-second unread grace, the composer keeps Stop while empty and shows the plain Send once typed, and the chat draws no scheduling machinery.
a608af6 to
ea02e57
Compare
Problem / Motivation
Goal: Record, as an accepted RFC, the product owner's decision that a crewmate DM answers a person who writes while it works: steer first, cancel after a 3-second unread grace, one Send (Stop while empty), and no scheduling machinery drawn.
On main a send to a busy crewmate offers the Steer / Queue / Jev-auto split, a queued message waits 36–38 s on a pod for the running turn to end, and it is drawn as a yellow queue card apart from the bubbles. #20240 changes that shape, and its First Principles lane asks for the decision on record.
Why it matters
A person talking to a crewmate does not know a turn is running. Asking them to pick a scheduling mode and then waiting half a minute makes the crewmate look stuck. The RFC writes down what was decided and what it costs, so the change is reviewed against a decision rather than against itself.
Not a goal
What changed (motivation → approach → change)
Goal → record the decision before the code lands →
docs/request-for-change/rfc-crewmate-responsive-send.md,accepted(product owner rayrayxu, 2026-10-15), plus one row indocs/request-for-change/README.md:Backwards compatibility
Compatible: documentation only; no code, config or schema changes.
Removes nothing: the PR adds one RFC and one index row.
Tests
N/A — documentation only.
scripts/docs-lint.shpasses.Manual verification
N/A — no runtime change.
Screenshots / video
N/A — documentation only. The implementing PR #20240 carries the pod screenshots.
Related Issues
Tracks #20181. Implementation: #20240.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license.