Skip to content

Commit 2f1a402

Browse files
Add design proposal: platform migration engine
Platform migrations are identified by a dense global integer that also serves as cluster state. Every new migration must claim the next number, so concurrent migration PRs conflict by construction; a single scalar cannot describe a branched history, so migrations are unbackportable; and the pending set comes from a number maintained in a different file than the migrations themselves, so silent skips are possible. The proposal replaces the integer with a content-addressed ID and an applied-set ledger, splits execution into a blocking pre-apply tier and an operator-driven background tier, and adds a machine-checkable contract around migration authoring: declared metadata, one shell dialect, a linter, and mandatory tests. Assisted-By: Claude <[email protected]> Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 93e347a commit 2f1a402

1 file changed

Lines changed: 346 additions & 0 deletions

File tree

  • design-proposals/platform-migrations

0 commit comments

Comments
 (0)