aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 04:44:05 +0000
committertv <tv@krebsco.de>2026-11-16 04:44:05 +0000
commit8c63e016c5fc1c4d2a3aefee5e1c8142ad876ad7 (patch)
tree30f12a816534ba7a209699632e188e44c3c6a1f7
parent041a0c0facadbe7cc8c7ef663a0b0c2ecc20f625 (diff)
federation: forks before remakes
Forks are what any group carries on by, and promise 3 rests on them; remakes are there only for Automerge's sake. Forks come at stage 4 and remakes at stage 5: until then a federated swarm that grows too large starts afresh by a fork whose version names the same parties, keys and rules. And a writer forked splits the nodes for good only until stage 2, where an operator may have its node drop what it took.
-rw-r--r--docs/federation.md15
1 files changed, 8 insertions, 7 deletions
diff --git a/docs/federation.md b/docs/federation.md
index b9bb42e..da4f7c7 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -811,23 +811,24 @@ On a federated swarm:
formats (a version's JCS bytes, hashes in paths and how two compare, the meta's
version); the bound on the writers a node starts in an epoch; 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.
+ carries. A node that doesn't know the policy stops taking changes. Until stage 5, a
+ federated swarm takes no remake: one that grows too large starts afresh by a fork
+ whose version names the same parties, keys and rules.
2. **What counts**, read by the current version and the keys; shown in the API.
Reports of the versions a node refused, and its operator having it drop what it
took; a tool reporting, from the votes, a party that voted twice.
3. **Nodes**: membership by the node lists and the party a node's own entry names, the
party shown in the handshake before that entry exists, a node syncing with members
only (a wire change), neighbours by party.
-4. **Remakes**: compaction only, each node building it from a base it holds, never on
+4. **Forks**: a swarm started from another's document, named by its first version and
+ the heads it names, and the check against it.
+5. **Remakes**: compaction only, each node building it from a base it holds, never on
its peers' word; the old epoch synced, while a node keeps it, with nodes still on it;
replay under the version current at the base.
-5. **Forks**: a swarm started from another's document, named by its first version and
- the heads it names, and the check against it.
6. **The registry**: the rules for krebs, the tool that signs kartei's entries in as
their parties', after the genesis change, and the one that reads them out.
Each stage's tests are its rows of Attacks. Each stage keeps every swarm that isn't
federated as it is, its tests passing untouched. A federated swarm made before the last
-stage is for tests: a later stage judges it otherwise. Until stage 5, a writer forked
-splits the nodes for good.
+stage is for tests: a later stage judges it otherwise. Until stage 2, nothing brings
+together the nodes a writer forked splits.