architecture-decision

An Architecture Decision Record documents significant technical choices by capturing context, alternatives, dependencies, engine compatibility, and consequences. It turns untracked architectural decisions into clear, reviewable records that preserve rationale and constraints over time.

You can retrofit existing ADRs using a dedicated retrofit mode that adds missing sections like engine compatibility and GDD traceability without modifying any existing content. This safely brings older decision records up to current architectural governance standards.

The best way to enforce GDD traceability in technical decision records is to run gated validation and GDD sync checks that prevent interface naming drift. This ensures architecture choices remain aligned with Game Design Documents throughout the development lifecycle.

You need an ADR when making significant architecture choices that require documented context, alternatives, and consequences. Creating an Architecture Decision Record ensures technical governance, engine compatibility risks, and dependency constraints are formally reviewed and preserved.

To validate engine compatibility risks when drafting architecture decisions, load mandatory engine reference materials to flag post-cutoff risks and ground the compatibility section in documentation. This prepares a risk-aware ADR validated through reviewer workflows.

Updating an architecture registry after creating an ADR requires explicit approval to optionally append new state ownership, interface contracts, forbidden patterns, and performance implications. This gated process ensures registry changes are reviewed before committing.