Product / Migrations
Review the evidence before a database change.
Evaluate migration scenarios, constraints, observations, and recovery evidence before deciding whether a change is ready.
- Scenario
- Old and new app versions overlap
- Constraint
- Both can read customer records
- Recovery
- Interrupted backfill resumes
- Review
- Evidence required for each stage
Why use Migrations?
A migration file describes a change. It does not show what happens when old code is still running, a backfill stops, or recovery is needed.
Review the transition
Organize evidence around the stages of the change, not just its final schema.
Make recovery part of review
Include interruption and recovery observations in the acceptance decision.
Keep unknowns visible
Identify which conditions the rehearsal evidence does not establish.
How Migrations fits your work
- 01
Define the scenarios
Supply the planned transition and the constraints it must preserve.
- 02
Bring rehearsal observations
Include stage results, compatibility checks, and recovery evidence.
- 03
Review the findings
Resolve failed or untested conditions before approving the actual migration.
What to know before you start
The website form evaluates supplied evidence. It does not run a database migration or certify zero downtime.
Use your workspace or a compatible agent connected through MCP. Read the connection guide.