diff options
| author | tv <tv@krebsco.de> | 2026-11-16 20:07:35 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 21:26:49 +0100 |
| commit | e32f4b6681f52659bc4c0e79c3be2b24f3d7495a (patch) | |
| tree | 2b2797282e3872dd335100e4779e057aab63be3d /docs/store.md | |
| parent | 9d18983e4b643eac04de49a42a6f29805570dba3 (diff) | |
docs: what of the store on Automerge is built
The store's design says what of it is built: on Automerge, a swarm holding a store,
started from its root or joined by its ID, each change judged by what it writes, and
the store a node reads from its document, by what is its own, putting again what the
document lacks, from a pinned checkpoint where there is one; not yet members by the fold,
the store at the API, and remakes, of which such a swarm takes no records or acks.
Diffstat (limited to 'docs/store.md')
| -rw-r--r-- | docs/store.md | 23 |
1 files changed, 14 insertions, 9 deletions
diff --git a/docs/store.md b/docs/store.md index 12276b4..32ce10e 100644 --- a/docs/store.md +++ b/docs/store.md @@ -2,15 +2,20 @@ A design, built stage by stage ([`federation.md`](federation.md), Stages): so far, the store held in memory (`federation::store`), with a fold made for its tests and the -federation's (`federation::fold`). 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. +federation's (`federation::fold`); and on Automerge, a swarm holding a store, started +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. 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 |
