1
Meta – Template ADR
Dmitrii Iurco edited this page 2026-06-11 15:39:28 -04:00

Status: Active | Owner: @roof | Updated: 2026-06-11

Meta – Template ADR

This is a copy-only skeleton. To use it: copy the full content into a new page named ADR – NNN Short Title.md (use the next available number), fill in each section, and delete this notice.

ADRs record significant architectural decisions — choices that are non-obvious, have consequences, or would be puzzling to a future maintainer without context.


> **Status:** Active | **Owner:** @username | **Updated:** YYYY-MM-DD

# ADR – NNN Short Title of the Decision

## Context

What situation or problem forced this decision? Include:

- What existed before (the old approach, or the absence of one).
- What constraints apply (security, performance, compatibility, team size).
- What would happen if no decision were made.

---

## Options Considered

List the realistic options that were evaluated.

### Option A — <Name>

What it is. Why it was considered. Key trade-offs.

**Rejected because:** <reason>.

### Option B — <Name>

What it is. Why it was considered. Key trade-offs.

**Rejected because:** <reason>.

### Option C — <Name> (chosen)

What it is. Why it was considered. Key trade-offs.

---

## Decision

State the decision in one or two sentences. Be specific.

> We chose Option C because <reason>. This means <concrete consequence>.

---

## Consequences

What changes as a result of this decision?

- List positive consequences (what it enables, what risk it removes).
- List negative consequences or trade-offs (what becomes harder, what is now constrained).
- List migration or compatibility concerns.
- List what must stay true for this decision to remain valid (invariants).