propagate-design-change

To trace architectural decisions after a Game Design Document update, analyze the impact of GDD changes on existing Architectural Decision Records to detect contradictions and resolve system integrity issues using automated impact assessment.

Architectural drift occurs when Game Design Document revisions invalidate or contradict existing technical decisions. Without traceability management, previously valid Architectural Decision Records become stale and fail to reflect current design intent.

Yes, you need git history access and structured ADR documentation to perform automated impact assessment. This access allows the system to identify revisions and resolve architectural inconsistencies caused by game design modifications.

To resolve contradictions between ADRs and updated game design documents, follow a resolution workflow that guides you through updating, superseding, or validating architectural decisions to ensure system integrity after a design pivot.

The best way to maintain traceability between design intent and technical implementation is to maintain clear links between Game Design Documents and Architectural Decision Records through automated impact analysis after design modifications.

You should supersede an Architectural Decision Record after a design pivot when automated impact analysis confirms the existing decision contradicts updated Game Design Document requirements and cannot be validated or simply updated.