Use Markdown Any Decision Records
#################################

Context and Problem Statement
=============================

We want to record any decisions made in this project independent whether decisions concern the architecture ("architectural decision record"), the code, or other fields.
Which format and structure should these records follow?

Considered Options
==================

* `MADR <https://adr.github.io/madr/>`_ 3.0.0 – The Markdown Any Decision Records
* Google Documents
* Confluence

Decision Outcome
================

Chosen option: "MADR 3.0.0", because

* Implicit assumptions should be made explicit.
  Design documentation is important to enable people understanding the decisions later on.
  See also `A rational design process: How and why to fake it <https://doi.org/10.1109/TSE.1986.6312940>`_.
* MADR allows for structured capturing of any decision.
* The MADR format is lean and fits our development style.
* The MADR structure is comprehensible and facilitates usage & maintenance.
* The MADR project is vivid.
* Google docs are not easily discoverable.
* We already spend too much time explaining past decisions.
