ADR-001: Start Project Decision ¶
1 Status ¶
| Date | Status | |
|---|---|---|
| ▶ | 07-07-2026 | Proposed |
2 Context ¶
This is an example decision record. It demonstrates how Almirah captures a
decision and links it to the requirements it affects.
3 Decision ¶
Describe the decision here. The leading "*" in the Status table marks the
4 Scope ¶
| # | Item | Owner | Depends On | Est (focused) | Est (safe) | Status | Start Date | Target Date | Description |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Requirements | BA | 2 | 3 | To Do | ||||
| 2 | Code | DEV | 3 | 5 | To Do | ||||
| 3 | Tests | TEST | 2 | 4 | To Do |
5 Out of Scope ¶
The ADR contains the most important sections with no detailed content.
6 Consequences ¶
6.1 Positive ¶
An ADR example will clearly show the approach Almirah framework use for any software changes.
6.2 Negative ¶
The format of this ADR can be different that is required for the real project.
6.3 Neutral ¶
7 Alternatives Considered ¶
- Add an empty
decisions/directory only. Rejected: an empty folder neither teaches the format nor causes the overview page to render, so it would not exercise the feature.
8 Affected Documents ¶
Table below shows a requirement whose text this decision creates or updates.
| # | Proposed Text | Req-ID |
|---|---|---|
| 1 | This is a first requirement (controlled paragraph with ID equal to "REQ-001"). | REQ-001 |
9 Software Versions ¶
| Software Version Category | Software Version ID |
|---|---|
| Latest Released Version | n/a |
| Issue Found in Version | n/a |
| Target Release Version | 0.0.1 |
10 References ¶
11 Review Evidences ¶
TBD