ADR-NNNN: Decision Title

Status: Proposed
Date: YYYY-MM-DD
Deciders: Role or team
Supersedes: None
Related roadmap/issue: Link or identifier

Context

Describe the code-derived problem, the forces that make a decision necessary, and the boundaries that cannot move. Link concrete source paths, behavior, and operational evidence.

Decision

State the chosen rule in direct language. Identify ownership, interfaces, authority, deployment effects, and compatibility behavior.

Alternatives considered

Alternative A

Summarize the approach and why it was not selected.

Alternative B

Summarize the approach and why it was not selected.

Consequences

Positive

• Outcome enabled by the decision

Negative

• Cost, constraint, or operational burden accepted

Migration and rollback

Describe data migration, compatibility window, rollout ordering, rollback boundary, and how mixed versions behave.

Verification

List tests, metrics, traces, deployment checks, and acceptance scenarios that prove the decision is implemented.

Architecture model updates

List every C4, dynamic-flow, deployment, risk, and guide page changed by this decision.