architect

The system-design layer between the PRD and the tasks: turns requirements into right-sized architecture — module/service boundaries, a data model, and interface contracts — with tradeoffs made explicit and never over-engineered. Decides the irreversibles (one-way doors) deliberately now, builds the simplest thing that serves the present, and places clean seams with concrete extraction triggers for the likely futures; every significant decision becomes an ADR with a trigger-to-revisit. An independent, read-only design-adversary challenges every boundary, data-model choice, and seam refute-first — embodying maestro's adversarial-verify, multi-vote always — and the surviving design is written into scribe's docs/ contract (docs/architecture/ + docs/adr/) as typed system facts verified against the code.