A joiner serves the history it adopted as a fragment - #165
Merged
Conversation
adopt_us installs the adder's group document as an automerge snapshot with an empty sedimentree tree, so the joiner held history it could not serve as items — to a device that syncs only with it, or to the store. A member holding applied history serves it the way compaction does: it builds a fragment. After adoption the joiner gives the document a single head (a signed merge anchor if needed) and builds one plaintext fragment over the whole adopted history, boundary empty, through the same install path compact uses. A third device enrolled by the joiner learns the first era from that fragment without ever meeting the founder.
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
2 participants
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.
After
adopt_usthe joiner builds oneusfragment over the adopted history (single head, empty boundary;install_fragmentshared withcompact), so it can serve that history to a peer or the store as sedimentree intends. Tests: joiner holds one fragment and a fresh engine rebuilds members from its bundle alone; A→B→C with C never meeting A; the joiner publishes the fragment to Drive. e2e 17/17 ×2. Automerge armed.