Repository navigation
Conversation
Contributor
|
Found 1 test failure on Blacksmith runners: Failure
|
This was referenced Oct 9, 2026
Contributor
Author
|
Superseded by #245, merged into next as d19cdd3. This exact branch head is an ancestor of the independently reviewed #245 head e1e6da9; its inactive persistent-storage groundwork is included in that cumulative change. Live guest delivery, retirement and ordinary persistent SQL remain open under NC05. |
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.
Persistent data needs a stable owner across independent compute generations. This adds an inactive enrollment layer over the closed owner codec: it synchronizes an exclusive pending intent before one original-create attempt, captures that attempt's exact volume identity, and promotes only after fresh guest/volume and private root/lock/record fences. Existing names, pending attempts, replacements and incomplete staging refuse. Existing-only retained reads preserve the original record and never create, adopt, repair or delete data.
The sealed transport requires atomic exclusive creation; Docker's idempotent volume-create API cannot provide that guarantee by itself. Only a stand-in implements the transport here. No CLI/runtime/provider activation is included. Failure after enrolled rename or directory synchronization remains uncertain, and a later data-only comparison does not prove the failed invocation completed or authorize effects. SQL retention, guest rollover, initializer lifecycle and full NC05 acceptance remain open.
This draft is stacked on #233's codec and targets
next. The finite model is registered with the maintained checker and distinguishes original-create, pending, publication, synchronization, failure and compute retirement; it does not qualify real durability or application data.Validation:
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.