Repository navigation
proposals: migrating stored IR across format versions - #171
Merged
Merged
Conversation
Seven pages under proposals/ir-migrations: the formats and the additive ledger, migration steps with explicit unknowns, running a migration safely, the proof plan and CI gate, hashes, pins and history, artifacts beyond the local store, and format 4 as the first client. Tracked in core#268.
2 of 18 tasks
added 3 commits
November 13, 2026 03:52
…ts reset at 1.0 Today's formats are out of scope and reset to a backup before 1.0, with the numbering restarting at format 0 at 1.0. Format 4 is the first real client; test-only formats prove composition and lossy steps. Drops the per-format fixture plans for formats 0 to 2 and the old-revs build job.
… decisions Migration and reset run only by explicit user commands (comline store migrate, comline store reset); other commands stop and name them. Every step has a down witness checked at migration time. Old pins that verify are accepted with a notice. Git merges across formats are refused. The 1.0 release refuses pre-1.0 stores, with an epoch stamp. Drops the older-binary hazard discussion and most open questions.
…npinned acceptances are re-asked
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Accepted, decided 2026-11-13. A design for migrating the stored IR (
.comline/) across format versions, so a format bump stops deleting every package's version history. Tracked in ComlineProject/core#268; relates to core#146 (reading older IR after 1.0) and core#222 (granular@unverified, which needs IR format 4).The proposal is under
docs/docs/proposals/ir-migrations/, linked from the proposals index andmkdocs.yml. Nothing is left open.Scope: the migration system and a proof that it is sound, not migrating today's formats, which reset at 1.0 when the numbering restarts. Format 4 (core#222 chains) is the first real client.
The rule: nothing is deleted or changed without the user doing so. Migration and reset run only by
comline store migrateandcomline store reset; every other command stops and names them. Read commands may migrate in memory.Pages:
SCHEMA.mdin core is the source.N -> N+1steps over frozen types, each with adownwitness and an explicit, fail-closed unknown.comline store migrate --check;reset;prune; a Git merge across formats is refused.downare accepted with a notice; compat and the changelog recompute from stored inputs and list what isunseen.accept_unverifiedentry is re-asked viacomline accept, never accepted.