propagate-design-change

To track the impact of a GDD change on existing ADRs, the process involves scanning your architectural decisions and comparing them against the revised GDD rules. It classifies affected ADRs as Still Valid, Needs Review, or Likely Superseded to prevent architectural drift.

Architectural drift occurs when updates to a Game Design Document make existing Architectural Decision Records stale or contradictory. Detecting this drift requires comparing the changed GDD sections against the original assumptions documented in prior ADRs.

To check if updated game design rules invalidate prior architectural decisions, compare the revised GDD against its previous git version and load ADRs using an architecture traceability index. This evidence-based comparison highlights conflicting requirements or tuning knobs.

Impact analysis for Godot ADRs does require reading the changed GDD and its previous git version. The git diff provides the evidence-based comparison needed to identify which specific design rule or formula changes invalidate prior architectural assumptions.

The best way to maintain architecture traceability when game design formulas change is to run an automated change impact assessment that cross-references the updated GDD with dependent ADRs. This guides targeted ADR follow-up and confirms safe updates through an optional director gate review.