# Delivery plan: [feature / change]

**State:** Proposed / Approved / In progress / Done
**Mode:** Planning only / Implementation authorized

## Outcome

[Behavior users or operators will see; concrete success criteria.]

## Evidence and current state

- Observed repository paths / interfaces:
- Known limitations and unsupported assumptions:

## Scope

- Included:
- Explicitly excluded:
- Affected public contracts, schemas, tenants, infra:
- Owning and dependent repositories, coordinating issue and linked member tasks (if multi-repository):

## Dependency-ordered slices

| Phase | Visible milestone | Files/boundaries | Verification | Prerequisites |
|---|---|---|---|---|
| 1 | [minimum useful behavior] | [modules] | [tests] | [decision] |
| 2 | [next independent behavior] | [modules] | [tests] | [phase 1] |

## Safety and rollout

- Compatibility strategy:
- Data migration and backfill (if relevant):
- Canary / feature flag / release order (if relevant):
- Rollback or forward-recovery:
- Cross-repository version/commit compatibility set, rollout order and partial-delivery recovery (if applicable):

## Risks and open decisions

- [Risk -> mitigation; owner if known]

## Definition of done

- [ ] Acceptance criteria met with observed evidence
- [ ] Relevant tests/lint/build checks run or gaps stated
- [ ] Architecture/contracts/docs and diagrams updated
- [ ] Rollout/rollback and telemetry considered where needed

## Execution log (only after execution begins)

- [Date / phase / observed evidence / blockers]