Production Database Change Protocol

Explicit invocation only — do not auto-activate on related context; wait for a direct request.

When to use

user needs to add, modify, rename, or remove a table, column, index, or constraint
user needs to create, inspect, apply, validate, or roll back a migration
a feature requires a schema change before application code can be written safely
user asks about migration status, schema drift, generated types, or live database state
a destructive, lock-sensitive, long-running, or hard-to-reverse DDL change is being considered
a schema change needs to be coordinated across application versions or deployments
Use for every schema or persistence change in this project
Use when reviewing migrations for safety, reversibility, compatibility, or modeling quality
Use when planning expand → backfill → contract changes
Use when diagnosing drift between live PostgreSQL state, migration history, and generated types