architecture-decision

To create an Architecture Decision Record, provide a title to initiate engine context loading, architecture registry checks, and a structured ADR draft capturing context, alternatives, dependencies, and consequences for your game engine architecture.

An Architecture Decision Record includes context, alternatives, dependencies, and consequences for domain-specific system design. It enforces GDD traceability checks and engine-reference validation gates to ensure technical decisions respect prior stances and engine constraints.

Yes, retrofit mode adds missing required sections to an existing Architecture Decision Record without modifying any present content. After adding sections, it prompts for re-validation through engine-reference and GDD sync checks.

Architecture Decision Records stay synchronized with a Game Design Document through built-in GDD sync checks. The workflow enforces cross-GDD traceability during validation and optionally updates the architecture registry with user-approved new stances.

Contradictory architectural stances are blocked by safety constraints. The workflow requires explicit user approval before making any architecture registry updates, ensuring no-regret decisions that respect prior stances and engine constraints.

Yes, the Architecture Decision Record workflow supports engine-specialist and technical-director review steps. After validation, a phase-gated closing workflow directs you toward remaining priority ADRs or next design-system and GDD tasks.