000 - Record architecture decisions
Date: 2022-03-19
Status
✅ Accepted
Context
As we build out our systems and services run by Developer Experience, we will need to make architectural decisions. These may be decisions about the tools and technologies we use, the way we structure our code, or the way we design our services. When making these decisions, we should record them, both to help us understand and remember why we made them, and to also act as a reference for onboarding new team members and to help teams working in related areas understand why we made them.
Finally, as outlined in the Government Design Principles, these should be publicly accessible as making things open makes things better.
Decision
We will record all significant architecture decisions as Architecture Decision Records (ADRs) in this repository, ensuring they remain publicly accessible and maintained over time.
Consequences
- Developers and service 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.