C.32.ADR:9 - Consequences

Consequence	Benefit	Cost
ADR is a publication projection.	Records stay readable while decision authority remains in PAD.	Authors must maintain the relation between record and decision.
Section functions are stable even when headings vary.	Software ADR, engineering memo, and certification rationale can be compared by function.	Local templates must be mapped rather than copied blindly.
Method and work effects are visible.	Developers can act on the decision instead of only reading rationale.	Records may need exact method refs and work-split refs.
Supersession is explicit.	Future readers can distinguish history from current decision.	Record packages need simple upkeep.