Status
Accepted
Context
We have started using Architecture Decision Records as our primary way to document the most important design decisions we take while developing Hydra Node, and this has proved effective in fostering fruitful discussions about major architecture changes.
During the course of this project, we have sometimes had debates on various topics leading to rejection of some ADRs. It could be the case that a previously rejected proposal turns out to be interesting, either because the context and situation have changed enough to reevaluate a proposal, or as background for some new proposal.
Decision
therefore
- We will keep rejected Architecture Decision Records alongside accepted and draft ones, in the same location and format
- Rejected ADRs must have tag
[Rejected]set
Consequences
Once attributed a serial number an ADR keeps it "forever", whether it's rejected or accepted