# ADR-XXXX: [Short descriptive title]

**Date**: YYYY-MM-DD **Status**: [Proposed | Accepted | Rejected | Deprecated |
Superseded] **Authors**: @author1, @author2 **Reviewers**: @reviewer1,
@reviewer2 **Deciders**: @tech-lead, @architect

## Context

Describe the architectural problem or challenge that needs to be addressed.
Include:

- What is the current situation?
- What forces are at play (technical, business, team, etc.)?
- Why is a decision needed now?

## Decision

State the architectural decision that was made. Be specific about:

- What solution was chosen
- Key implementation details
- Timeline for implementation

## Rationale

Explain why this decision was made. Include:

- Analysis of alternatives considered
- Pros and cons of the chosen approach
- Key factors that influenced the decision
- Trade-offs that were accepted

## Alternatives Considered

### Option 1: [Name of alternative]

- **Description**: Brief description of the alternative
- **Pros**: List the advantages
- **Cons**: List the disadvantages
- **Decision**: Why this was/wasn't chosen

### Option 2: [Name of alternative]

- **Description**: Brief description of the alternative
- **Pros**: List the advantages
- **Cons**: List the disadvantages
- **Decision**: Why this was/wasn't chosen

## Implementation

### Technical Changes Required

- [ ] Code changes in specific services/modules
- [ ] Database schema changes
- [ ] Infrastructure updates
- [ ] Configuration changes

### Migration Plan

If applicable, describe:

- Steps to migrate from current to new approach
- Backward compatibility considerations
- Rollback strategy

### Testing Strategy

- Unit test requirements
- Integration test requirements
- Performance testing needs
- Security testing considerations

## Impact Assessment

### Services Affected

- **Service Name**: Description of impact
- **Service Name**: Description of impact

### Performance Impact

- Expected latency changes
- Resource usage implications
- Scalability considerations

### Security Implications

- New security risks introduced
- Security controls that need updates
- Compliance considerations

### Operational Impact

- Monitoring/alerting changes needed
- Documentation updates required
- Training needs for team members

## Metrics & Success Criteria

Define how success will be measured:

- **Performance metrics**: Response time targets, throughput goals
- **Quality metrics**: Error rates, availability targets
- **Business metrics**: User satisfaction, adoption rates

## Timeline

- **Decision deadline**: YYYY-MM-DD
- **Implementation start**: YYYY-MM-DD
- **Rollout complete**: YYYY-MM-DD
- **Review/evaluation**: YYYY-MM-DD

## Dependencies

- External dependencies (third-party services, libraries)
- Internal dependencies (other team deliverables)
- Infrastructure dependencies (cloud resources, etc.)

## Risks & Mitigation

| Risk             | Impact       | Likelihood   | Mitigation Strategy         |
| ---------------- | ------------ | ------------ | --------------------------- |
| Risk description | High/Med/Low | High/Med/Low | What we'll do to address it |

## Communication Plan

- Who needs to be informed of this decision?
- What documentation needs to be updated?
- Any training or knowledge sharing sessions needed?

## References

- Links to related issues, pull requests
- External documentation or research
- Previous ADRs that relate to this decision
- Relevant RFCs or specifications

---

## Review Notes

### Review 1 (YYYY-MM-DD)

- **Reviewer**: @reviewer-name
- **Comments**: Summary of feedback
- **Action items**: What needs to be addressed

### Review 2 (YYYY-MM-DD)

- **Reviewer**: @reviewer-name
- **Comments**: Summary of feedback
- **Action items**: What needs to be addressed

## Amendment History

| Date       | Author  | Change                | Reason                  |
| ---------- | ------- | --------------------- | ----------------------- |
| YYYY-MM-DD | @author | Description of change | Why the change was made |
