# Schema-breaking migrations

M13 models schema-breaking intent, typed adapter steps and an explicit irreversible marker. It does
not execute user SQL, Python, shell or paths. Production planning requires the stronger M12 approval
boundary and explicit rollback/irreversibility facts; automatic cutover is denied.

Known future adapters may model expand, dual-compatible operation, migrate, verify, cutover and
contract. Each step must be compiled into trusted application code and versioned in the adapter
fingerprint. M13 deliberately makes no generic rollback claim for irreversible work.