| 1 |
The ID (ADR-NNNN, 4-digit) matches the filename number and is unique and sequential (Mandatory) |
Pass |
ID ADR-0001 matches adr-0001-... and is the first ADR. |
| 2 |
Context states the problem, the forces (cost, risk, constraints) and the options evaluated (Mandatory) |
Pass |
Context states the criterion, the stakeholders S02 and S03 and three options. |
| 3 |
At least two options were considered, or the absence of alternatives is justified (Mandatory) |
Pass |
Three options were evaluated. |
| 4 |
Decision is stated in one or two unhedged sentences and matches one of the evaluated options (Mandatory) |
Pass |
The decision is one sentence and equals option 2. |
| 5 |
Consequences list both Positive and Negative outcomes (Mandatory) |
Pass |
Positive and Negative lists are present. |
| 6 |
Quality-attribute impacts (performance, security, portability, etc.) are named where the decision affects them (Optional) |
Pass |
Portability across Windows, Debian and macOS is named. |
| 7 |
Affected Artifacts are listed as links, and each is also in CrossReference (Mandatory) |
Pass |
Affected Artifacts BC-001, SA-001 and MIL-002 are also in CrossReference. |
| 8 |
Status changes are recorded as new Version History rows with a Change summary and Commit link; retained rows are never rewritten (Mandatory) |
Pass |
First version; row is Proposed then Accepted by this review. |
| 9 |
A superseded or deprecated ADR names its successor, and the successor links back (Optional) |
N-A |
No superseded ADR. |
| 10 |
Written in business or technical language of the domain, with no unexplained abbreviations (Optional) |
Pass |
Abbreviations are used as in the Business Case; CSV is spelled by the module name. |
| 11 |
Status is one of Proposed, Accepted, Rejected, Deprecated or Superseded by ADR-NNNN, and every Version History row uses only these (Mandatory) |
Pass |
Status values are Proposed and Accepted. |
