Operations
Migration Reset
Destructive reset strategy for platform and runtime schema alignment
Strategy
This platform is still greenfield.
That means migration work should optimize for:
- clean schema language
- clean bounded contexts
- clean operational behavior
Not for backwards compatibility.
Reset sequence
- drop and recreate platform and tenant runtime databases
- run rewritten platform migrations
- run rewritten runtime migrations for each tenant
- reseed canonical platform data
- reseed runtime data where needed
- verify bootstrap and smoke
Why
Keeping old migration history that encodes old thinking is low-value debt.
The reset should leave the platform with:
- tenant-first naming
- registry-first app model
- worker config in platform state
- runtime parity across tenant DBs