solution-architect

To design production-grade system architecture, you analyze project constraints like scale, team, and budget to generate deliverables including ADRs, system diagrams, API contracts, and data models. This process derives the architecture directly from your specific project limitations and business needs.

Generating API contracts and data models involves analyzing your project constraints and producing OpenAPI, gRPC, AsyncAPI definitions, ERDs, and SQL migrations. The output adapts to your selected tech stack and scales according to your team size and compliance requirements.

Yes, this architecture design approach supports multiple engagement modes from Express to Meticulous. These modes adapt the discovery depth and output detail, allowing you to balance the thoroughness of architecture generation against your project timeline.

The best way to scaffold a project root with services and libraries is to derive the structure from constraint-driven architecture design. This method generates your initial project configuration files and service directories based on the documented architecture decisions and selected tech stack.

Yes, you can use Architecture Decision Records to document tech stack selection for a new project. The system architecture design process generates ADRs alongside system diagrams and data models, ensuring every technology choice is justified by your specific scale, budget, and compliance constraints.

You should not use automated system architecture design when your project lacks defined business requirements or clear constraints like scale and budget. The process relies heavily on analyzing these specific project parameters to generate tailored architecture deliverables and scaffold the codebase.