ADR-XXXX: [Short Descriptive Title]¶

Status: Proposed | Accepted | Superseded | Rejected | Deprecated

Date: YYYY-MM-DD

Deciders: [Names or roles, e.g., "Architecture Working Group", "Tech Leads"]

Tags: [Optional: component, domain, e.g., "observability", "security", "data"]

Context¶

[2-4 paragraphs describing the situation, problem, or requirement that led to this decision. Include: - What problem are we solving? - What constraints exist? - What are the business/technical drivers?]

Decision¶

[1-2 paragraphs stating the decision clearly and concisely. Be specific about what is being decided.]

We will [specific action/choice].

Options Considered¶

Option 1: [Name of Option]¶

Description: [What this option entails]

Pros: - [Benefit 1] - [Benefit 2]

Cons: - [Drawback 1] - [Drawback 2]

Option 2: [Name of Option]¶

[Same structure as Option 1]

Option 3: [Name of Option]¶

[Same structure as Option 1]

Rationale¶

[2-3 paragraphs explaining why the chosen option was selected. Reference specific pros/cons, constraints, or requirements that drove the decision.]

Consequences¶

Positive¶

[Expected positive outcome 1]
[Expected positive outcome 2]

Negative¶

[Expected negative outcome 1]
[Expected negative outcome 2]

Neutral / Trade-offs¶

[Trade-off or neutral consequence]

[Link to design doc, RFC, or implementation guide]
[Link to best-practices document]
[Link to runbook or operational guide]

Implementation Notes¶

[Optional: Brief notes on how this decision will be implemented, key milestones, or dependencies]

References¶

[Optional: Links to external resources, research, or benchmarks that informed the decision]