| 1 |
The ID (ADR-NNNN, 4-digit) matches the filename number and is unique and sequential |
Pass |
ID ADR-0001 matches the file name adr-0001 and is the first ADR. |
| 2 |
Context states the problem, the forces (cost, risk, constraints) and the options evaluated |
Pass |
Context states the problem, the forces and the two options. |
| 3 |
At least two options were considered, or the absence of alternatives is justified |
Pass |
Two options: four-layer layout, flat package. |
| 4 |
Decision is stated in one or two unhedged sentences and matches one of the evaluated options |
Pass |
Decision is two sentences, unhedged, and is option 2. |
| 5 |
Consequences list both Positive and Negative outcomes |
Pass |
Consequences list three positive and three negative outcomes. |
| 6 |
Quality-attribute impacts (performance, security, portability, etc.) are named where the decision affects them |
Pass |
Maintainability and flexibility impacts are named (later refactoring). |
| 7 |
Affected Artifacts are listed as links, and each is also in CrossReference |
Pass |
Affected Artifacts BC-001 and MIL-002 are links and are 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 |
First version; Version History has one row. |
| 9 |
A superseded or deprecated ADR names its successor, and the successor links back |
Pass |
Not superseded or deprecated; not applicable to the status, so the row passes by absence. |
| 10 |
Written in business or technical language of the domain, with no unexplained abbreviations |
Pass |
Plain technical language; abbreviations are the framework's own IDs. |
| 11 |
Status is one of Proposed, Accepted, Rejected, Deprecated or Superseded by ADR-NNNN, and every Version History row uses only these |
Pass |
Status is Accepted, an allowed value. |
