orchestrator-architect

System architecture design generates architecture decision records, component diagrams, data models, and API surfaces to define the technical blueprint for a new microservice. It includes integration designs and tech stack justifications tailored to your requirements.

An architecture decision record for system design documents your tech stack justifications, API surfaces, and data models. It serves as a standalone deliverable capturing the rationale behind component diagrams and failure mode analysis.

Yes, you can generate API surfaces and data models without a full planning framework. This standalone architecture design session focuses solely on producing technical deliverables when upstream PM and Security requirements are provided as context.

Yes, system architecture design includes failure mode analysis and scaling considerations. These are generated alongside integration designs and system component diagrams to ensure the technical blueprint accounts for edge cases and growth.

The best way to document tech stack justifications is through architecture decision records generated during a standalone architecture design session. This captures the reasoning behind your chosen frameworks and platforms alongside API contracts and data models.

You need to provide PM and Security requirements as upstream context before initiating system architecture design. These inputs drive the generation of accurate architecture decision records, data models, and failure mode analysis.