design-doc-high-level

To generate a high-level architecture design document, input your approved requirements document and interactively clarify runtime, compute, storage, networking, security, deployment, and observability decisions. The output includes Mermaid diagrams and decision rationale for stakeholders to review.

A high-level architecture design includes major component boundaries, technology selection rationale, and Mermaid diagrams for data models, data flows, and security boundaries. It explicitly keeps implementation details out of scope while establishing the system shape for stakeholder review.

Yes, evaluating technology choices for deployment and observability is a core part of this architecture design process. The interactive clarification specifically targets these decisions, ensuring your technology selection includes documented rationale for runtime, compute, and storage choices.

Yes, the architecture design process produces Mermaid diagrams specifically for system boundaries, data models, and data flows. These visual documentation elements help stakeholders review the proposed system shape before implementation begins.

You need a high-level architecture design document when a team has an approved requirements document and requires a reviewable architecture proposal. It applies to product planning, system architecture discovery, and review cycles for new or evolving software systems before implementation.

The main limitation of a high-level architecture design document is that implementation details are explicitly kept out of scope. It focuses purely on choosing the right system shape and technology stack, deferring detailed implementation decisions for later phases.