| 1 |
The ID (ADR-NNNN, 4-digit) matches the filename number and is unique and sequential |
Pass |
ADR-0001 matches adr-0001-*.md and follows the registry sequence. |
| 2 |
Context states the problem, the forces (cost, risk, constraints) and the options evaluated |
Pass |
Context states the problem, forces and the options evaluated. |
| 3 |
At least two options were considered, or the absence of alternatives is justified |
Pass |
Three options (ADR-0001) / three options (ADR-0002) are listed. |
| 4 |
Decision is stated in one or two unhedged sentences and matches one of the evaluated options |
Pass |
The Decision is stated plainly and is one of the listed options. |
| 5 |
Consequences list both Positive and Negative outcomes |
Pass |
Positive and Negative consequences are listed. |
| 6 |
Quality-attribute impacts (performance, security, portability, etc.) are named where the decision affects them |
Pass |
Portability and security: no runtime dependency to install or patch. |
| 7 |
Affected Artifacts are listed as links, and each is also in CrossReference |
Pass |
Affected Artifacts are links and each is in CrossReference. |
| 8 |
Status changes are recorded as new Version History rows with a Change summary and Commit link; retained rows are never rewritten |
Pass |
One Version History row; no retained row was rewritten. |
| 9 |
A superseded or deprecated ADR names its successor, and the successor links back |
N-A |
No ADR is superseded or deprecated. |
| 10 |
Written in business or technical language of the domain, with no unexplained abbreviations |
Pass |
Plain technical language; abbreviations such as CSV are spelled out in the Business Case. |
| 11 |
Status is one of Proposed, Accepted, Rejected, Deprecated or Superseded by ADR-NNNN, and every Version History row uses only these |
Pass |
The status is Accepted, an allowed value. |