diff options
| author | tv <tv@krebsco.de> | 2026-11-16 21:31:15 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 23:04:46 +0100 |
| commit | 96eacbbd2df4127920976fc2e7c4efc53cd83f52 (patch) | |
| tree | b3de0414b0e9472d49486e3436b4b1b7826f3a8c | |
| parent | 9fa28bb06692cd3e9d06b678d3dfe2595d328a5f (diff) | |
docs: the store at a node's API is built
The store's design says that the store at a node's API is built: putting events, and
showing what counts, what it refused, and its operator's drops.
| -rw-r--r-- | docs/store.md | 22 |
1 files changed, 12 insertions, 10 deletions
diff --git a/docs/store.md b/docs/store.md index 2c255f4..3ba60d1 100644 --- a/docs/store.md +++ b/docs/store.md @@ -8,16 +8,18 @@ writes (`access::holding`), and the store a node reads from its document, by wha own, putting again what the document lacks, from a checkpoint its operator pins if it 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. +party's and those its operator names, and taking no token another node issued; and the +store at a node's API (`api::events`), putting events and showing what counts, what it +refused, and its operator's drops. Not yet: 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 |
