# Workflow: schema diff as an approval gate

## Goal
No restore or migration runs without a human- or CI-readable summary of what it changes.

## Steps
1. Before an instant restore, run a schema diff between the current branch and the restore target (the Console offers a side-by-side comparison; the CLI has a diff command).
2. Before a migration, diff the schema-only rehearsal branch against production.
3. Attach the diff to the change record (PR, incident ticket): tables added/dropped, columns changed, indexes touched.
4. Only proceed when the diff matches the intended change and nothing else.

## Ordering constraints
- Diff before the operation, not after; after is an autopsy.

## Traps
- Data-only changes do not show in a schema diff; pair it with row-count checks for restores.
- Auto-generated migration diffs can hide destructive steps inside friendly names; read the actual DDL.

## Verify
The last three restores/migrations each have a diff attached to their change record, and at least one caught an unintended change.