diff options
Diffstat (limited to 'docs/store.md')
| -rw-r--r-- | docs/store.md | 24 |
1 files changed, 16 insertions, 8 deletions
diff --git a/docs/store.md b/docs/store.md index ffca117..dad1485 100644 --- a/docs/store.md +++ b/docs/store.md @@ -68,13 +68,18 @@ can't build the checkpoint takes it where its operator pins it. A node builds every checkpoint it moves to itself, from the one before and the events up to the new heads, and judges every event after it. A checkpoint it can't build, as it was away across a move and a remake after it, or as it joins, it takes only where its -operator pins it, by its ID, and then judges every event after it as any. A node joining -starts from a checkpoint its operator pins; only for a store that never moved does the -root its operator names, the swarm's ID, suffice. Once a store moved, what came before -its checkpoint can be grown anew from the root by what the fold refuses since (the -federation: keys of versions long replaced, [`federation.md`](federation.md), -Checkpoints), and a node joining from the root would take it. So a node takes nothing on -a peer's word: what it didn't build or judge itself, its operator vouched for. +operator pins it, by its ID, and then judges every event after it as any. It finds it in +its document: the document's checkpoint, or one the fold moves to at the history of an +event the document holds (the federation: a version naming one), built at those heads +from what the document holds, as any node builds it; the document holds what that takes, +from the document's checkpoint on (On Automerge, What the store takes from the +document). A node joining starts from a checkpoint its operator pins; only for a store +that never moved does the root its operator names, the swarm's ID, suffice. Once a store +moved, what came before its checkpoint can be grown anew from the root by what the fold +refuses since (the federation: keys of versions long replaced, +[`federation.md`](federation.md), Checkpoints), and a node joining from the root would +take it. So a node takes nothing on a peer's word: what it didn't build or judge itself, +its operator vouched for. ## The fold @@ -250,7 +255,10 @@ would take them from anywhere: each once it holds its dependencies, judged at it history, and by the node's own (A node's own). The rest it reads none of: an event nobody takes, or one a checkpoint forgot, stays in the document until the next remake leaves it out (Remakes). Which change put an event, and how often, changes nothing, so -honest nodes hold one document, whatever each reads from it. +honest nodes hold one document, whatever each reads from it. A node reads its store from +its document anew whenever it starts, from the document's checkpoint or the one its +operator pinned, by its own refusals and its operator's drops, which it keeps in a file +(A node's own): it keeps nothing else of the store across a restart. **A node puts again**, in changes of its own, every event its document lacks that a store starting at the document's checkpoint would take, but for the node's own refusals and |
