aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/federation.md4
-rw-r--r--docs/store.md16
2 files changed, 11 insertions, 9 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 2eb01b8..91ba4a2 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -823,8 +823,8 @@ continuum builds and behaves as it does, and its tests pass untouched.
version names the same parties, keys and rules.
4. **Forks**: a store whose root is a checkpoint at another's heads, named by its root,
checked by the nodes holding that history.
-5. **Remakes**: compaction only, the snapshot holding the store as it is at its base,
- and every event beyond it put again.
+5. **Remakes**: compaction only, the snapshot holding the store read from the document
+ up to its base, and every event beyond it put again.
6. **The registry**: the rules for krebs, the tool that signs kartei's entries in as
their parties', after the root, and the one that reads them out.
diff --git a/docs/store.md b/docs/store.md
index 3051f44..12a5e34 100644
--- a/docs/store.md
+++ b/docs/store.md
@@ -286,13 +286,15 @@ every swarm: acks tell an honest coordinator when to commit, and bind nobody. A
holding a store takes compaction only, whose snapshot is a function of its base and its
record (its ID, its coordinator): two remakes at one base are two epochs.
-* **The snapshot** holds the store as the node reads it at the base: its checkpoint,
- where it isn't the root, the events it keeps and those after it, each at its ID; the
- policy; and of continuum's protocol data what a compaction carries, but the entries of
- nodes that aren't members at the base. What a checkpoint forgot, and events nobody
- takes, leave the document here. Nodes that read the store differently at the base (the
- sides of keys that voted twice, in the federation) build different snapshots, and part
- here.
+* **The snapshot** holds the store a node reads from the document up to the base,
+ starting at the document's checkpoint, by its own refusals and drops: the checkpoint
+ it reaches there, where it isn't the root, the events that one keeps and those after
+ it, each at its ID; the policy; and of continuum's protocol data what a compaction
+ carries, but the entries of nodes that aren't members at the base. What that
+ checkpoint forgot, and events nobody takes, leave the document here. A node that moved
+ to a later checkpoint since the base builds the snapshot as one that didn't, as both
+ read the document; nodes that read the store differently at the base (the sides of
+ keys that voted twice, in the federation) build different snapshots, and part here.
* **A node follows a decision** whichever node coordinated it: a decision reaches it
only through a member, which could decide one itself, and a remake changes no event.
It builds the snapshot itself, from a base it holds, and checks it against the