orchestration-design

To generate an architectural design document, you need a process that reconstructs architecture from verified facts and aligns recommendations with your existing codebase. This ensures the resulting design is grounded in evidence and repository constraints.

Constraint adjudication in software architecture design is the process of interpreting and classifying requirements from a brief into hard or soft constraints. It flags ambiguities to ensure the architectural approach adheres to verified limitations.

To ensure your architecture design fits your current codebase patterns, perform a repository fit check that inspects existing code structures. This assessment compares proposed solutions against current patterns to identify alignment or divergence.

You can ground architectural recommendations using external documentation by integrating live web searches and version-sensitive guidance. This ensures your design decisions are based on up-to-date, evidence-backed research rather than assumptions.

The best way to handle ambiguous requirements in a design brief is through a user alignment loop that iteratively refines the design based on feedback. This process classifies constraints and flags ambiguities for clarification before finalizing the architecture.

You should avoid using first-principles design from a brief when you lack a validated brief or cannot inspect existing code patterns. Without verified facts and repository alignment, the generated design may not integrate properly with your current codebase.