create-architecture

To create a master architecture document, synthesize approved CDDs, module indexes, ADRs, and reference libraries into a single blueprint. This process maps modules to architecture layers, defines ownership, and establishes ADR traceability for technical governance before implementation begins.

Defining API boundaries and data flow requires analyzing how information moves through system layers and specifying public contracts between modules. A master architecture blueprint formalizes these boundaries by mapping module responsibilities, exposures, and consumption patterns across the technical design.

Auditing ADRs for traceability involves checking existing decision records against current product requirements to identify gaps. The architecture review process highlights missing formal records and verifies that technical decisions align with the approved concept and module index.

Yes, repository context and existing architecture files can be read to generate technical design and layer ownership definitions. The system synthesizes this context to map modules to specific architecture layers, clarifying exactly what each module owns, exposes, and consumes.

You need a formalized architecture blueprint when preparing for implementation and requiring rigorous technical governance. It replaces ad hoc design notes by satisfying technical requirement extraction, risk-aware technology verification, phased approval workflows, and final handoff documentation.