create-architecture

To generate a master architecture blueprint, consolidate your GDDs, systems index, and ADRs to produce layer maps, data flow diagrams, and API boundaries. This process translates approved design documents into a single actionable architecture document.

Game architecture system design handles engine compatibility by verifying engine APIs against reference files and flagging HIGH to MEDIUM risk changes. This enforces review gates to prevent fragmented decisions and misaligned engineering efforts across engine versions.

A technical requirements baseline for system design includes a numbered list extracted from engine reference files, GDDs, and existing ADRs. It provides the foundational constraints needed to produce module ownership tables and prioritized required ADRs.

Yes, you can use ADRs to trace module ownership by running an ADR audit within your architecture document. This establishes clear API boundary contracts and generates a prioritized list of required new ADRs for technical director sign-off.

The best way to consolidate GDDs and engine reference files is through a collaborative, incremental workflow that writes approved sections directly to an architecture markdown file. This ensures all technical constraints and design decisions are captured in a single blueprint.

You need a master architecture document when your project faces fragmented decisions and misaligned engineering efforts across multiple GDDs. It becomes necessary to translate approved design documents and engine constraints into a concrete, implementable blueprint.