architecture-decision

To prevent architecture contradictions, document technical decisions by creating Architecture Decision Records that check architectural registry stances, ensuring new choices do not contradict existing system constraints before writing.

An Architecture Decision Record is a formatted document capturing significant technical decisions, including context, alternatives, and consequences. You need an ADR when defining engine or domain-specific architecture choices to keep your project reviewable.

To link architecture decisions to GDD requirements, the ADR authoring process traces the technical choice to relevant Game Design Document systems and performs a naming sync check to verify alignment before finalizing the record.

Yes, you can add missing sections to an existing ADR without changing current content by using the optional retrofit mode, which appends required sections like Status and Engine Compatibility while preserving all present material.

Yes, the ADR process includes engine compatibility by loading engine reference documentation to verify constraints, and enforces quality through automated engine specialist and technical director review gates before finalizing.

The limitation of retrofitting an Architecture Decision Record is that the retrofit mode strictly adds only missing sections without modifying any present content, meaning existing formatting errors or incorrect stances in the original document remain uncorrected.