aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 04:14:20 +0000
committertv <tv@krebsco.de>2026-11-16 04:14:20 +0000
commit3b4b0ef9ad295b358023dd659caf3f14e950a514 (patch)
tree40b8875212a31ee4637115a004446eb9689371b2 /docs/federation.md
parent37ddd429652f5a8764c6035078b4e4e3bd663714 (diff)
federation: sizes among what the federation's number names
Nothing bounded a version, a key set, a node list, a path or a value: a version larger than a sync message carries would be written where it passed and reach nobody, and nodes built with different bounds would take different changes. The sizes each may have are the federation's number's, each within what a sync message carries, and stage 1 sets them.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md19
1 files changed, 11 insertions, 8 deletions
diff --git a/docs/federation.md b/docs/federation.md
index d8ffc46..ed36660 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -668,6 +668,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang
| 72 | A party's first envelope at a place another's envelope holds | Names that one as `prev`, its `seq` one more; anew, refused | unit |
| 73 | A federation's genesis change holding more than its first version gives (values, votes, a topology) | A node joining builds it and doesn't join one that differs | sim |
| 74 | Two federations started under one swarm name | None: a federation is named by its first version's hash | unit |
+| 75 | A version, set, list, path or value larger than the federation allows | Refused; none can be too large for a sync message | unit |
## Roads not taken
@@ -736,12 +737,12 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang
Every node of a swarm runs the same version of continuum today. A federated swarm's
parties can't be made to upgrade together, so from the first federated swarm on,
-continuum's releases work together in one, and what all its nodes must agree on is
-named by the federation's number: the rules of this design, the envelope and how the
-value of a place is read, what makes a change one Automerge writes, how a path and a
-version are spelled and read, which version a node takes and which is current, the
-remake's snapshot, its replay and its order, and the Automerge version, whose encoding
-fixes a change's hash.
+continuum's releases work together in one, and what all its nodes must agree on is named
+by the federation's number: the rules of this design, the envelope and how the value of
+a place is read, what makes a change one Automerge writes, how a path and a version are
+spelled and read, the sizes each may have, which version a node takes and which is
+current, the remake's snapshot, its replay and its order, and the Automerge version,
+whose encoding fixes a change's hash.
A change to the federation is a design like this one, with the next number. A swarm
moves to it by a version of its policy that names it (`"federation": 2`), which the
@@ -778,8 +779,10 @@ On a federated swarm:
every change touching what the federation reads (versions, proposals, votes, key
sets, node lists), as `access::screen` moves it today for what continuum's rules
read; the byte formats (a version's JCS bytes, hashes in paths and how two compare,
- the envelopes a version sets, the meta's version). A node that doesn't know the
- policy stops taking changes. Until stage 4, a federated swarm takes no remake.
+ the envelopes a version sets, the meta's version), and the sizes a version, a set, a
+ list, a path and a value may have, each within what a sync message carries. A node
+ that doesn't know the policy stops taking changes. Until stage 4, a federated swarm
+ takes no remake.
2. **What counts**, read by the current version and the keys; shown in the API.
Reports of a party that voted twice, and of versions a node refused.
3. **Nodes**: membership by the node lists and the party a node's own entry names, the