# Plan a model migration without dropping requirements — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] Current model/endpoint identity and representative application requests.

- [ ] Candidate specifications and a held-out case set with required modalities, context and output behaviour.

## Output checks

- [ ] Requirements come from actual application contracts or fixtures.

- [ ] Unknown capability remains distinct from supported and unsupported.

- [ ] Every required evaluation ID has one observed result.

- [ ] Rollout and rollback triggers use observable application signals.

## Deliverables

- [ ] Requirement/capability matrix

- [ ] Held-out evaluation ledger

- [ ] Cost and operational comparison

- [ ] Canary and rollback proposal

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- Benchmark position does not prove tool-call, vision or application compatibility. Missing, duplicate or failed required evaluations block a preflight pass.

- API calls, private input transfer and a canary can incur cost or affect people. The local checker runs none of those actions and does not verify vendor specifications.

Workflow: https://undominated.ai/workflows/#plan-a-model-migration