propagate-design-change

To detect stale ADRs after a GDD update, scan all ADRs and the traceability index to locate references to the changed design document and classify assumption impacts. This process compares prior assumptions against current GDD text to identify outdated architectural decisions.

The best way to perform impact analysis on architecture decisions is to extract ADR traceability and compare assumptions against revised requirement specifications. This generates a classified impact report categorizing decisions as still valid, needing review, or likely superseded.

You compare previous GDD versions to current assumptions by retrieving the prior git-based version of the design document and matching it against ADR traceability. This comparison highlights conflicting assumptions caused by renamed requirements or adjusted tuning knobs.

You cannot automatically update architectural decision records, as the workflow uses a technical-director approval gate before writing any outputs. It guides per-ADR resolution actions and produces an impact report without making destructive edits to ensure safe governance.

Yes, the ADR impact analysis workflow supports retrieving previous document versions via git diff to establish a baseline for comparison. This allows you to accurately identify which architectural decisions are affected by the latest design document edits.

You should run ADR traceability extraction during architecture governance workflows whenever a GDD is edited, requirements are renamed or removed, formulas and acceptance criteria change, or tuning knobs are adjusted to ensure implementation consistency.