ADR-NNNN: Short imperative title

Status

Proposed | Accepted | Deprecated | Superseded by ADR-NNNN

Date

YYYY-MM-DD

Deciders

Names / roles

Related

ADO work items, other ADRs, design-journal entries

1. Context

The situation that forces a decision. Describe what the system does today (or proposes to do), what problem this creates, and what forces push in different directions. This is the most important section — future readers will evaluate the decision against the context, so be concrete.

If the decision is driven by operational reality rather than technical constraint, say so. Include an example scenario.

2. Decision

The rule. Imperative voice. Short. A reader should be able to implement the rule from this section alone.

3. Consequences

What becomes easier, what becomes harder, and what is deliberately sacrificed. Use bullet lists under each heading.

3.1. Positive

  • …​

3.2. Negative

  • …​

3.3. Neutral

  • …​

4. Alternatives Considered

For each serious alternative, write one paragraph: what it was, why it was rejected, and under what conditions it would become the right choice. This is the "why not the other way?" record.

4.1. Alternative A: …​

Why rejected.

4.2. Alternative B: …​

Why rejected.

5. References

  • Design journal: design-journal/YYYY-MM/thread-name.adoc (session dates)

  • ADO: #NNN (Feature), #NNN (US), …​

  • Code: path/to/file.java (class / method if relevant)