SchemaVersioning

Incremental, scripted database schema changes tied to code releases — Localz's backend already has migrations 004-008 from round 1.

Why we need this / what value this brings

Incremental, scripted migrations are what let the schema evolve safely alongside deployed code, with a clear history.

When to use this

Every schema change, without exception — never hand-edit a production schema directly.

How to use or implement this

Write each migration as a small, reversible step; test the rollback path, not just the forward path, before relying on it (Localz's backend already has migrations 004-008 from round 1).

Research questions

• What migration tool is in use (Alembic?) and is there a documented rollback story for a bad migration?

---

Empty folder — drop notes, links, and findings here as you research.