When a team forgets why it chose a design, the same debate can start all over again. A decision scribe records significant architectural choices and their rationale, preserving the reasoning for later and helping new developers catch up. The role is more than taking notes: it creates certainty and a lasting record. section 2.3
Capture the decision in an Architecture Decision Record (ADR), a short written record of:
- The problem context and the significant choice made. section 2.3
- Options considered, including reasons for rejecting alternatives. section 2.3
- The rationale behind the choice, so the team can revisit it without repeating old arguments. section 2.3
