aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 10:39:28 +0000
committertv <tv@krebsco.de>2026-11-16 10:39:28 +0000
commitc8663d869be0ef719cc234da51d8f4924ef0d864 (patch)
tree28f7c2dcd0e7eedb6dd36d5f1255269908ccb561
parente4e24cad0c65bbf0bb0cdbb8d1fe1b5b36ad94a2 (diff)
federation: acks bind nobody in a federated swarm
Continuum lets a member ack another remake of its epoch only once the first is aborted, and in a federated swarm only the coordinator aborts: a coordinator gone after proposing stalled every remake of its epoch. Read the other way, as a remake left undecided binds nobody, members moved on, and a coordinator back late decided beside the remake they moved to: two decisions, from honest nodes alone. Acks bind nobody: a member may ack another remake without the first aborted, and an honest coordinator decides only while the acks it counts are still for its remake.
-rw-r--r--docs/federation.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 9cca39b..afe48d8 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -496,10 +496,12 @@ 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: 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:
+fewer nodes are away, and a node follows a decision without counting them. They bind
+nobody: a member may ack another remake of its epoch without the first aborted, and an
+honest coordinator decides only while the acks it counts are still for its remake. 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