aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 20:53:31 +0000
committertv <tv@krebsco.de>2026-11-16 22:04:33 +0100
commitd22ca4351b86c0066f13e735960838bb5d85e044 (patch)
tree7133af3554e47daa9672d5bb240362b83ec36c02
parentaf087a816f870ea943c61624d496b1d5e4d090b9 (diff)
docs: members by the fold are built
The store's design says that members by the fold are built: each node of the party its operator names, syncing with members only, its neighbours among them and some among its own party's and those its operator names, and taking no token another node issued.
-rw-r--r--docs/store.md22
1 files changed, 12 insertions, 10 deletions
diff --git a/docs/store.md b/docs/store.md
index 32ce10e..2c255f4 100644
--- a/docs/store.md
+++ b/docs/store.md
@@ -6,16 +6,18 @@ federation's (`federation::fold`); and on Automerge, a swarm holding a store, st
from its root or joined by its ID (`document::events`), each change judged by what it
writes (`access::holding`), and the store a node reads from its document, by what is its
own, putting again what the document lacks, from a checkpoint its operator pins if it
-pins one (`federation::held`). Not yet: members by the fold, the store at a node's API,
-and remakes, of which a swarm holding a store takes no records or acks. The store holds
-events. Each event is named by the hash of its bytes and names the events it builds on;
-it is judged where it was written, at that history, so every node judges it alike; and
-the events a node holds read as one state. The store starts from a checkpoint, the state
-at some heads written down, and holds what came after it; moving to a later checkpoint,
-a node forgets what matters no more, so that it holds what is relevant and nothing else.
-What the events are, how one is judged, what they read as and when the store moves to a
-checkpoint is a **fold**'s, and the store is generic over it. The federation
-([`federation.md`](federation.md)) is its first fold.
+pins one (`federation::held`); and members by the fold, each node of the party its
+operator names, syncing with members only, its neighbours among them, some among its own
+party's and those its operator names, and taking no token another node issued. Not yet:
+the store at a node's API, and remakes, of which a swarm holding a store takes no
+records or acks. The store holds events. Each event is named by the hash of its bytes
+and names the events it builds on; it is judged where it was written, at that history,
+so every node judges it alike; and the events a node holds read as one state. The store
+starts from a checkpoint, the state at some heads written down, and holds what came
+after it; moving to a later checkpoint, a node forgets what matters no more, so that it
+holds what is relevant and nothing else. What the events are, how one is judged, what
+they read as and when the store moves to a checkpoint is a **fold**'s, and the store is
+generic over it. The federation ([`federation.md`](federation.md)) is its first fold.
The store asks nothing of what carries its events. It is built first inside a swarm's
Automerge document (On Automerge): continuum's sync, transports, saving and remakes