diff options
| -rw-r--r-- | docs/store.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/store.md b/docs/store.md index 5a1a9bc..d554a7a 100644 --- a/docs/store.md +++ b/docs/store.md @@ -220,10 +220,11 @@ ID, as bytes; each making the maps on its way as continuum writes a path 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, 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. +way and filled in the order of their IDs: events go into a change until their bytes +there reach 1 MiB, and the next event begins the next change, so that whether a change +is whole is a question of that change alone. 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 |
