bts-architectlisted

# Architect Force the decomposition choice to be a **judgment between alternatives**, not the first thing that comes to mind. One proposed decomposition is a default, not a decision. ## Prerequisites 1. `domain.md` exists and passes `bts verify domain.md` (invariant ownership clean) 2. `scope.md` Status: CONFIRMED 3. `research/v1.md` exists AND contains an `## Official Guidance` section (per bts-research Step 3.5). If the section is missing, gather it NOW before proposing alternatives: identify the stack from scope.md / project-map.md and fetch the platform's officially recommended architecture per `.claude/rules/bts-evidence-policy.md` (Context7 → official docs → site-filtered search). Append the findings to the research doc with `Source:` lines. Do NOT propose decompositions from imagination while the vendor's own guidance sits unread. If any prerequisite fails, STOP and point the user at the missing step. ## Step 1: Propose alternatives (min 2, max 4) **Grounding rule**: when the platform has an officially recommended architecture (research `## Official Guidance`), EXACTLY ONE alternative MUST be that pattern applied to this feature's domain — carrying its official `Source:` URL. It may lose the debate to a simpler decomposition, but it must be on the table; rejecting it requires a stated reason in the decision block's Rejected list. For each alternative, produce: - **Name** — short kebab-case identifier, e.g. `state-machine-centric`, `