# Architecture Spec

Use this for cross-system, high-impact, or difficult-to-reverse changes.

## Context
Why is an architecture change needed?

## Problem
What architectural problem or constraint are we addressing?

## Goals
- 

## Non-goals
- 

## System context
Which systems, teams, users, and external dependencies are involved?

## Current state
Describe the relevant architecture today.

## Proposed boundaries
What responsibilities belong where? What must remain separated?

## Data ownership and flow
- System of record:
- Data movement:
- Consistency expectations:
- Retention / lifecycle:

## Interfaces and contracts
Document APIs, events, schemas, protocols, or compatibility requirements.

## Security and privacy
- Authentication:
- Authorization:
- Sensitive data:
- Trust boundaries:
- Audit requirements:

## Reliability and operations
- Availability:
- Failure modes:
- Recovery:
- Observability:
- Capacity / scale:

## Migration and compatibility
How can this be introduced without unsafe disruption?

## Alternatives considered
### Option A
Benefits:
Trade-offs:

### Option B
Benefits:
Trade-offs:

## Architecture decisions
Capture important decisions and why they were made.

## Acceptance criteria
- [ ] 
- [ ] 

## Risks
- 

## Open questions
-