Decision records¶
How to use: every decision that affects scope, method, the research question, tooling, or process gets an Architecture Decision Record (ADR) within 48 hours. Copy ADR-template.md, number it sequentially, open a pull request, and link the decision issue. Every decision, big or small, also gets a row in docs/workspace/DECISION_LOG.md.
Status values: Proposed, Accepted, Superseded by ADR-NNNN, Rejected.
| ADR | Title | Status | Date |
|---|---|---|---|
| 0001 | Run the project with Scrum plus a Lean Six Sigma overlay | Accepted | 2026-09-13 |
| 0002 | Select the topic by proposal issues and a ranked ballot | Superseded by ADR-0005 | 2026-09-13 |
| 0003 | Repository structure, tooling, and branch policy | Accepted | 2026-09-13 |
| 0004 | Topic selection: proposal P-01 | Accepted | 2026-09-14 |
| 0005 | Run the project as a solo project | Superseded by ADR-0006 (2026-09-15) | 2026-09-14 |
| 0006 | Reinstate the four-person group | Accepted (members confirm at the 2026-09-16 kickoff) | 2026-09-15 |
| 0007 | Keep the official sample as the population for RQ1 to RQ3 | Proposed | 2026-09-28 |
Rubric note: the retrospective must also record changes to the research question, method, scope, or interpretation. Link the ADR from the retrospective file.