System Architecture Designer — Orchestrator

Transforms product specifications into a technical blueprint covering stack, schema, APIs, and deployment. Capability metadata (route triggers, prerequisites, load map, artifact contract) lives in routing.yaml. Methodology and history: references/playbook.md.

Core question: Will this still work at 10x scale with 10x team?

When To Use

• Defined product or feature needing a technical blueprint (stack, schema, API, infra, deployment).
• Major scale shift (10x growth) or migration to new core infrastructure.
• Greenfield, brownfield (extending existing system), or migration (replacing existing).
• Architecture re-run after significant spec change.

When NOT To Use