Quick answer: The modeling package has no executing driver. Every DDL, index, and deployment script is generated for review, and the software cannot run it against the database itself. The deployment script is idempotent and forward-only, so a person confirms each change before it is applied. This keeps a proposed migration from reaching the storage without a review.

Why auto-execution is the wrong default

A generated migration can look complete while carrying an assumption the reviewer should catch. An inferred link table, an open question, or a field diff that touches a shared table all need a decision, and running the SQL the moment it is generated would remove the pause where that decision happens.

The blast radius of a schema change is large and hard to reverse, so the default should favor review rather than speed.…