aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 04:44:28 +0000
committertv <tv@krebsco.de>2026-11-16 04:44:28 +0000
commite44cd86fb02c0c0dd1177e9dc9d7dc35b3efbe02 (patch)
treef6b34d03d8b2ad68583296b008148764f43c221d /docs/federation.md
parent4e1594883ce22a2bc08b1f34ab8e85b4013f78f6 (diff)
federation: what acks are for in a federated swarm
Acks stay continuum's, by node, but in a federated swarm a node follows a decision it can build without counting them, so what they decided was nobody's to say. They tell an honest coordinator when to commit, so that fewer nodes are away; they are no safeguard.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 14b8f24..4748a49 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -491,9 +491,11 @@ start one, and sign into it, after the genesis change, what they keep.
A remake starts the document anew, for Automerge's sake only (Where Automerge sets
limits); the federation needs none and asks for none. When to remake, and who acks, is
-continuum's as in every swarm. A federated swarm takes compaction only, whose snapshot
-is a function of its base and its record (its ID, its coordinator): two remakes at one
-base are two epochs. What a federated node asks of a remake:
+continuum's as in every swarm: acks tell an honest coordinator when to commit, so that
+fewer nodes are away, and a node follows a decision without counting them. A federated
+swarm takes compaction only, whose snapshot is a function of its base and its record
+(its ID, its coordinator): two remakes at one base are two epochs. What a federated node
+asks of a remake:
* **It builds it itself.** A node that holds an epoch leaves it only for one whose
snapshot it built itself, as continuum's node builds a compaction's and checks it