You're offline — showing cached data

MC-4372

Make MC Architect design-aware and Reviewer browser/test-aware
2026-06-13 08:47:07 SAST
Home Board MC-4372

Make MC Architect design-aware and Reviewer browser/test-aware

Elmar reviewed https://github.com/russelleNVy/three-man-team and agreed MC should keep the simple Architect / Builder / Reviewer mental model, with two explicit additions: 1. A...
State Done Next Action Closed Owner Luci Runtime Closed Age 16d ago
MC-4372
Ticket is done; runtime is closed. · profile claude_opus_1m_high · cwd /home/lucienne/workspace/mission-control · uptime 16d 0h · last activity 15d 19h ago

Description

MC-4372
Elmar reviewed https://github.com/russelleNVy/three-man-team and agreed MC should keep the simple Architect / Builder / Reviewer mental model, with two explicit additions: 1. Architect responsibility must include design quality before build starts: - Every non-trivial UI/user-facing ticket brief must include design intent, target user flow, mobile/desktop expectations, and acceptance criteria. - Architect must check whether existing MC design standards / current product direction apply before dispatching Builder. - If the task is UI-visible, Architect should decide whether Tessa/mobile/design evidence is required up front, not after the implementation claims done. 2. Reviewer responsibility must include real user-browser use and tests: - Reviewer must not only inspect code/diff against the brief. - Reviewer must verify tests/smokes appropriate to the change. - For browser/user-facing work, Reviewer must run or require live browser use evidence: real route, console/DOM sanity, screenshots where applicable, and 375px mobile evidence when mobile-visible. - Reviewer should fail work that only has DOM/unit proof but no real user-flow/browser evidence for UI-facing changes. Goal: - Update MC workflow/gate prompts, WAT role copy, runtime architecture/docs, and/or reviewer dispatch prompts so this becomes a durable invariant. - Keep the Three Man Team simplicity in the user-facing model: Architect designs/briefs, Builder builds, Reviewer tests like a user + verifies code/tests. - Do not add noisy extra roles by default; use Tessa/Atlas/council as hidden/specialist gates when risk/UI/architecture warrants them. Acceptance criteria: - Architect/briefing path has explicit design-intent checklist for UI/user-facing work. - Reviewer/gate path has explicit browser-use + test-evidence checklist. - Existing Tessa/mobile visual gate remains compatible; do not duplicate it, wire the reviewer expectation into it. - A small smoke/demo ticket or test proves a UI-visible change cannot be approved with code-only evidence. - Update docs/runtime-architecture-refresh.md if system behavior changes. Related existing work: MC-4207 role-based gates, MC-4303 Tessa as user tester, MC-4326 mobile visual gate, MC-4343 controller/reviewer/Tessa smoke. Expected check-in: within 2 hours with implementation path or blocker.

Activity

done
Luci is working...
Live
No activity yet
Help