System Design Orchestrator

Own the state lifecycle and phase gates. Select capabilities by need and hand off a standard envelope; do not assume sibling skills can directly call one another. Read references/capability-map.md for routing and references/contract-v1.md plus references/handoff-v1.md for the local contract.

Lifecycle

1. Initialize or validate system_design_state and preserve its design_id.
2. Route requirements framing, then capacity modeling, architecture/domain decisions, data topology and consistency, failure analysis, and validation.
3. After each handoff, merge only the returned state_patch; preserve stable IDs and record provenance in traceability.
4. Limit blocking questions to three per interaction. Turn non-blocking gaps into explicit assumptions with confidence and owner.
5. Keep interview focused on high-impact unknowns and provisional decisions. In production, require evidence, operational ownership, security/compliance boundaries, recovery targets, and testable gates.
6. Do not mark complete until failure analysis exists, validator status is PASS, and all required phase gates are satisfied. A missing capability uses a safe fallback: emit the expected input/output contract, add an open question and risk, and keep status in_progress or blocked.

Complexity rule

For microservices, sharding, Kafka/event streaming, multi-region, or polyglot persistence, require a measurable requirement, capacity threshold, risk, or organizational constraint, plus a simpler alternative, rejection reason, operational cost, and evolution path. Otherwise record the simpler architecture as the default.

Output