# Technical Plan

This document explains how the approved spec will be implemented. Do not use it to quietly change the requirements.

## Spec
Link or path:

## Repository observations
Existing patterns, components, dependencies, and constraints that affect the implementation.

## Proposed approach
Describe the implementation approach and why it fits the repository.

## Components affected
| Area | Change | Reason |
| --- | --- | --- |
| | | |

## Data / API changes
- 

## Security considerations
- 

## Failure handling
- 

## Test strategy
- Unit:
- Integration:
- Contract:
- End-to-end:
- Other:

## Verification
Use the repository's real commands.

```text
<build / lint / typecheck / test / verify commands>
```

## Rollout / migration
- 

## Risks and mitigations
- 

## Open technical questions
-