Evolve Your Schema

Kizaki treats schema evolution as a first-class workflow. The recommended path is always:

1. edit your Inspire schema
2. generate a committed migration
3. review the plan
4. apply locally
5. deploy

This is how Kizaki keeps schema work fast without turning it into hidden local state. The schema is easy to change, but every real database change still becomes reviewable and repeatable.

Create The Next Migration

kizaki migrate plan --name add_project_status

Review the generated files under migrations/<NNNN_slug>/:

• plan.inspire
• snapshot.json

The most important file to review is plan.inspire. That is where you confirm that Kizaki understood your intent correctly.

Apply Locally

kizaki migrate apply

kizaki dev uses committed migrations as the local source of truth. If your schema moves ahead in a schema-affecting way without a committed migration, startup fails closed and tells you what to do next.

That fail-closed behavior is intentional. It prevents local development from quietly drifting into a state that is hard to reproduce or deploy later.

Runtime-Only Changes

Not every Inspire change needs a migration. Policy-only and runtime-only changes can hot-reload without changing the database schema.

The practical rule is:

• if the database shape changes, plan a migration
• if only runtime behavior changes, you usually do not need one

Next Step

When your app is ready, continue with Deploy Your App.