Files
lmnp-organizer/docs/adr/0022-reset-development-data-instead-of-migrating.md
T

558 B

Reset development data rather than preserving compatibility

Status: accepted

The application is not in production, so existing development data and contracts are not compatibility constraints. Until an explicit later decision declares production data must be preserved, domain and schema changes replace obsolete Mongo documents, reference data, and API contracts directly; all callers and tests are updated together, and development data is deleted or reseeded instead of adding migrations, compatibility adapters, or transitional read/write paths.