template.md

layout	adr	title	status	deciders	date	technical-story
page	adr-number	short title of solved problem and solution	proposed | rejected | accepted | deprecated | … | superseded by	<!-- optional --> list everyone involved in the decision <!-- optional -->	<!-- optional --> YYYY-MM-DD when the decision was last updated <!-- optional -->	<!-- optional --> description | ticket/issue URL <!-- optional -->

Context and problem statement

[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in form of a question.]

Decision drivers

• [driver 1, e.g., a force, facing concern, …]
• [driver 2, e.g., a force, facing concern, …]
• …

Considered options

• [option 1]
• [option 2]
• [option 3]
• …

Decision outcome

Chosen option: "[option 1]", because [justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force force | … | comes out best (see below)].

Positive consequences

• [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]
• …

Negative consequences

• [e.g., compromising quality attribute, follow-up decisions required, …]
• …

Pros and cons of the options

[option 1]

[example | description | pointer to more information | …]

• Good, because [argument a]
• Good, because [argument b]
• Bad, because [argument c]
• …

[option 2]

[example | description | pointer to more information | …]

• Good, because [argument a]
• Good, because [argument b]
• Bad, because [argument c]
• …

[option 3]

[example | description | pointer to more information | …]

• Good, because [argument a]
• Good, because [argument b]
• Bad, because [argument c]
• …

Links

• Refined by ADR-0005
• …