architect-teamlisted

# /architect-team — Coordinated Design Council ## Overview Three perspectives on a design instead of one, deployed as a unit: | Agent | Perspective | Model | |---|---|---| | `architect` | Independent judgement — boundaries, coupling, the simpler alternative, what's ADR-worthy. **Advise-only.** | opus | | `code-architect` | Structure — folder/module organisation, layering, naming conventions | sonnet | | `backend-architect` | Server side — API/system design, auth, performance, deployability | sonnet | | `database-architect` | Data layer — schema/indexing/query-optimisation/migrations/integrity (composable; pulled when the data model is non-trivial) | sonnet | **Advisory-first contract:** this council *designs and critiques*; it doesn't ship code. `architect` never implements. The output is an agreed design + the ADRs it warrants. Implementation is a separate, approved step. This is the council to deploy **whenever anything architecture-related is being reviewed, worked on, or analysed** — a new feature/module, a refactor of code organisation, a service boundary, or "what's the right shape for X?". ## When to Use - **Standalone:** "how should I structure the X feature?", "review this design before I build it", "is this the right service boundary?". - **As the design stage inside execution:** before writing plans turns a spec into tasks, or mid-flight when an approach needs a sanity check. Feeds the agreed design into the plan. - Whenever a change is hard-to-reverse o