Skip to content

ADR-NNNN: [Decision Title]

Metadata

Status: Proposed | Accepted | Deprecated | Superseded · Date: YYYY-MM-DD · Deciders: [names] · Tags: [tags]
Related PRD: [Link or N/A] · Supersedes: [ADR-NNNN or N/A] · Superseded By: [ADR-NNNN or N/A]

Tech Strategy: ✅ Follows Golden Path OR ⚠️ Deviation — see Rationale


Context

[What is the problem or situation that motivates this decision? Include technical constraints, business goals, and current gaps. Be specific — link to entities, services, or files where relevant.]


Decision Drivers

  • [Driver 1: e.g., must not block streaming response]
  • [Driver 2: e.g., backward compatible with existing API]
  • [Driver 3: e.g., configurable without redeploy]
  • [Driver 4: e.g., team has limited Redis ops experience]

Considered Options

Option 1: [Name]

[Brief description]

Pros Cons
[Pro 1] [Con 1]
[Pro 2] [Con 2]

Option 2: [Name]

[Brief description]

Pros Cons
[Pro 1] [Con 1]
[Pro 2] [Con 2]

Option 3: [Name] (if applicable)

[Brief description]

Pros Cons
[Pro 1] [Con 1]

Decision Outcome

Chosen Option: Option N — [Name]

Rationale: [Why this option over the others. Reference the Decision Drivers. Be explicit about trade-offs accepted.]

Quantified Impact (where applicable)

Metric Before After Notes
Latency (p99) [X] ms [Y] ms
Cost $[X]/mo $[Y]/mo
Throughput [X] req/s [Y] req/s

Consequences

Positive:

  • [Consequence 1]
  • [Consequence 2]

Negative:

  • [Consequence 1]
  • [Consequence 2]

Risks:

  • [Risk 1 and mitigation]

Validation

  • [ ] Performance benchmarks meet requirements (if applicable)
  • [ ] Security review completed (if applicable)
  • [ ] Tech Strategy alignment confirmed
  • [ ] Related plan document created: docs/plans/plan-[topic].md


Changelog

Date Author Change
YYYY-MM-DD [Name] Initial draft