Revision control
Copy as Markdown
# 0. Use Markdown Architectural Decision Records
Date: 2025-10-09
## Status
Proposed
## Context
We need to record the architectural decisions made on this project.
## Decision
We will use Architecture Decision Records, as described by Michael Nygard in [this article](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions).
## Consequences
### Positive
- One ADR describes one significant decision for a specific project.
- The consequences of one ADR are very likely to become the context for subsequent ADRs.
- Developers and project stakeholders can see the ADRs, even as the team composition changes over time.
- The motivation behind previous decisions is visible for everyone, present and future.
## References
- [Michael Nygard's article](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions)
- [iOS eng Presentation](https://docs.google.com/presentation/d/1hnA-TbBiXVbEdkLyxoAAyAwZrIYBjbkBu7-Egisk_GA/edit?usp=sharing)
- [Earn maintainers esteem with ADRs](https://understandlegacycode.com/blog/earn-maintainers-esteem-with-adrs/#adrs-are-simple-markdown-files)