# Keep the old decision when you replace it

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Keep the old decision when you replace it

ID: MHC-D-RESEARCH-1013 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/keep-the-old-decision-when-you-replace-it

Deleting the old rationale makes the past look less reasonable than it was.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A technical choice is changing and future readers will need to understand both versions.

### Avoid when

- An architecture decision record is not a diary for every minor edit. Preserve confidential details only in approved locations and correct factual errors transparently.

### Explanation

Keep a short decision record with the forces present at the time, the choice and its consequences. When a new decision replaces it, mark the old record as superseded and link the replacement. Preserve history without presenting an obsolete choice as current guidance.

### Template

Decision: [choice]. Context and constraints: [context]. Status: [status]. Consequences and trade-offs: [effects]. Replaces or is replaced by: [link].

### Example

A team replaces a batch interface with an event-based one. The earlier record retains the volume and platform constraints that originally justified batching.

### Check

A reader can identify the current decision and explain why the earlier one existed.

### Limits

- An architecture decision record is not a diary for every minor edit. Preserve confidential details only in approved locations and correct factual errors transparently.

### Evidence and sources

- supports: Nygard's architecture decision records preserve context, decision, status and consequences, retaining superseded decisions with a reference to their replacement. — RS-475C7CFA24D02071. An ADR records a decision and its rationale, not proof that the decision was correct or remains suitable. (Format; Status; Consequences)
- RS-475C7CFA24D02071: Documenting Architecture Decisions — https://www.cognitect.com/blog/2011/11/15/documenting-architecture-decisions

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/trace-a-requirement-to-the-reason-and-test-that-justify-it
