propagate-design-change

To check which ADRs are affected by a GDD revision, scan your architecture traceability index to detect decisions referencing the changed GDD. The tool categorizes each ADR as Still Valid, Needs Review, or Likely Superseded by comparing assumed requirements against current GDD sections.

Architectural drift occurs when existing ADRs become stale after GDD revisions. Prevent drift by propagating design changes to identify mismatched ADRs, classify their validity, and reconcile them through per-ADR resolution while updating the traceability index.

Propagate design changes by running the propagation command with your revised GDD path. It compares each referenced ADR against current GDD sections, generates a categorized change impact report, and supports per-ADR resolution to keep, update, or supersede decisions.

You can validate ADR impact analysis results by running an optional technical director gate for validation. This gate checks the categorized impact report before you choose how to resolve each affected ADR and commit traceability updates.

Yes, this architecture maintenance workflow requires git as a dependency to manage GDD revisions and ADR updates. It operates within your existing git-tracked repository to detect changes and maintain traceability across architectural documents.

Supersede an ADR when the current GDD sections directly contradict the assumed requirements of the decision. The propagation tool classifies this as Likely Superseded, whereas partial mismatches are categorized as Needs Review for targeted updates.