supersede

Superseding an Architecture Decision Record involves creating a new ADR that explicitly replaces the old one while preserving the original document for historical integrity. The process verifies the decision chain and displays dependency graphs to identify related decisions requiring updates.

You need to supersede an ADR instead of editing it directly when a previous architecture decision is no longer valid and must be replaced by a new decision. Supersession maintains a controlled transition and preserves the decision-making history without rewriting past records.

Yes, ADR supersession requires explicit user approval before making any changes to the old ADR. This user approval workflow minimizes the risk of mistakes and ensures a controlled replacement of old decisions with new ones.

You can identify related architecture decisions by reviewing the dependency graph displayed during the supersession process. This graph shows the dependencies of the target ADR, helping you see which other decisions may need updating based on the new changes.

Managing code governance for architecture decisions is best handled by using ADR supersession to control how old decisions are replaced. This approach ensures decision record integrity through dependency checks, explicit approvals, and maintaining a clear chain of supersession.

The metadata does not specify whether multiple ADRs can be superseded simultaneously. The standard workflow guides you through superseding a single target ADR, verifying its decision chain and dependencies before proceeding with the replacement.