Keep a Notebook Through a Risky Migration
Work from the brief alone. Write what you would produce — actors, requirements, data, a first slice, your unknowns — before opening anything below it; the exercise stops working if you read the reality first.
The store must move order storage to a new schema without downtime. Keep an engineering notebook through the work: current goal, assumptions, unknowns, decisions with evidence and alternatives, experiments with predictions, findings, next step. Use an AI as a reviewer and debugging partner where it helps, and record what you asked and what you did with the answer.
Your attempt
Nothing here is checked. It exists so that the reveal below is a comparison rather than a reading.
Asking the AI to produce the migration plan and executing it. It will be a reasonable plan, and the first anomaly will find an engineer who cannot say which step assumed what — because the assumptions were never theirs — and the notebook, if it exists, records outcomes without reasons.
Read this even if you are confident. It is here rather than behind a button because it is the move most people actually make, it produces things that look like a project, and its cost arrives when the first hard requirement has nowhere to go.