Learn the Standard
Adopt an Existing Database
Begin future SQL-first work without pretending unrecorded hosted history is known.
Do not invent migration history
When tables already exist in Supabase without reliable Git-tracked history, do not write a fictional initial migration and call it applied. That would hide drift rather than control it.
Inspect before changing
Collect a sanitized read-only view of tables, columns, constraints, indexes, RLS state, policies, grants, function security, exposed schemas, Storage buckets/policies, and platform settings relevant to your application. Do not include rows, tokens, customer data, or private object URLs in an AI prompt or a public artifact.
Begin tracked work from a reviewed baseline
- Save a dated sanitized schema snapshot only after live inspection.
- Document that earlier hosted changes predate protocol adoption.
- Identify the first new migration that will use the commit, apply, verify, and deployment-record procedure.
- Never backfill historical deployment receipts unless evidence actually exists.