diff options
| author | tv <tv@krebsco.de> | 2026-11-16 15:41:10 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 16:52:53 +0100 |
| commit | 4d59242f510ac25ff1aca31526e6e3fa9c8d7a11 (patch) | |
| tree | 592dd820861eb4b839592cae021f342a53c52a8b | |
| parent | 8d02b92626016ec9045aae1382ac28b0df89f3ee (diff) | |
docs/store: the changes every node builds
An epoch's first change, and a fork's changes after it, carry no node's signature, so
the rule that a change carries one now sets them aside. Their writer, derived from the
root or from the remake, is one anyone can compute, so it writes exactly the changes
every node builds, and any other change under it is refused: nobody commits a change of
that writer and number before the one every node builds, and parts the nodes. The
genesis change writes the policy (a map, keys sorted), the swarm's ID (a string) and the
root, in that order; a fork's kept events fill its later changes in the order of their
IDs, each up to 1 MiB of events.
| -rw-r--r-- | docs/store.md | 30 |
1 files changed, 19 insertions, 11 deletions
diff --git a/docs/store.md b/docs/store.md index ea5b416..6eee7c4 100644 --- a/docs/store.md +++ b/docs/store.md @@ -204,14 +204,18 @@ document holds nothing but the store and continuum's protocol data. | `_continuum/swarm` | the swarm's ID: the root's | | elsewhere under `_continuum` | continuum's protocol data, as far as this says | -The **genesis change**, the swarm's first, writes the policy, the swarm's ID, its epoch -and the root, and nothing else, built byte for byte from the root: its writer the first -16 bytes of the root's ID, time 0, no message. So one root makes one swarm, and a node +The **genesis change**, the swarm's first, writes, in this order and nothing else: the +policy at its place, as a map with its keys sorted; the swarm's ID at +`_continuum/swarm`, as a string, as continuum's genesis records it; and the root at its +ID, as bytes; each making the maps on its way as continuum writes a path +(`store::write_path`). It is built byte for byte from the root: its writer the first 16 +bytes of the root's ID, time 0, no message. So one root makes one swarm, and a node joining builds the genesis change and checks it. A fork's genesis change holds its root -alone; the events the root keeps follow in changes of the same writer, each holding up -to 1 MiB of them, in the order of their IDs, all built the same way. Continuum reads the -policy as one asking for signed changes, as a strict one does, and nothing else of a -strict policy: the document holds no values but events. +alone; the events the root keeps follow in changes of the same writer, built the same +way and filled in the order of their IDs: an event goes into the change being filled, +unless its bytes would take the events there past 1 MiB, and then it begins the next. +Continuum reads the policy as one asking for signed changes, as a strict one does, and +nothing else of a strict policy: the document holds no values but events. ### What a change writes @@ -227,10 +231,14 @@ Everything else is closed, a write at, within or above it refused: whatever isn' `_continuum`, users, bans, logouts, sessions, forgotten nodes, `_continuum/access` with the policy's place, the swarm's topology (`neighbours`, `relays`, `topology`, `dissemination`), and whatever a later continuum adds. Nothing deletes or replaces an -event. A change carries its node's signature, as a strict swarm's changes do, and is -first of all one Automerge itself writes (Where Automerge sets limits). Every node -judges a change by these alone, each a question of the change and its history, and -refuses it with everything built on it, as continuum refuses a change its rules refuse +event. A change carries its node's signature, as a strict swarm's changes do, but for +the changes every node builds itself: an epoch's first change, and a fork's changes +after it. They carry none, and their writer, derived from the root or from the remake +*(checked: `remake::snapshot`)*, writes exactly them: any other change under that writer +is refused, so nobody commits under it what every node doesn't build. A change is first +of all one Automerge itself writes (Where Automerge sets limits). Every node judges a +change by these alone, each a question of the change and its history, and refuses it +with everything built on it, as continuum refuses a change its rules refuse ([`access.md`](access.md), Changes judged on every node). It judges no event there: which events it takes is its store's (below). The same event put by two changes at once is one event: its key holds the same bytes twice. |
