| 1 |
The ID (ADR-NNNN, 4-digit) matches the filename number and is unique and sequential |
Pass |
ADR-0002 in adr-0002-s01-approves-as-stand-in.md. |
| 2 |
Context states the problem, the forces (cost, risk, constraints) and the options evaluated |
Pass |
Names the roles, the conflicting text in SA-001 and the Business Case, and the framework rule. |
| 3 |
At least two options were considered, or the absence of alternatives is justified |
Pass |
Three options. |
| 4 |
Decision is stated in one or two unhedged sentences and matches one of the evaluated options |
Pass |
Two sentences; matches option 2. |
| 5 |
Consequences list both Positive and Negative outcomes |
Pass |
Two positive, three negative. |
| 6 |
Quality-attribute impacts (performance, security, portability, etc.) are named where the decision affects them |
Pass |
Security and accountability impacts are named; the missing second reader is the first negative. |
| 7 |
Affected Artifacts are listed as links, and each is also in CrossReference |
Pass |
SA-001 and RC-001 are linked and cited. |
| 8 |
Status changes are recorded as new Version History rows with a Change summary and Commit link; retained rows are never rewritten |
Pass |
Initial row only. |
| 9 |
A superseded or deprecated ADR names its successor, and the successor links back |
N-A |
Nothing is superseded. |
| 10 |
Written in business or technical language of the domain, with no unexplained abbreviations |
Pass |
IT Professional English; roles are given by ID. |
| 11 |
Status is one of Proposed, Accepted, Rejected, Deprecated or Superseded by ADR-NNNN, and every Version History row uses only these |
Pass |
Accepted only. |
