aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/federation.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md
index da4f7c7..14b8f24 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -545,10 +545,13 @@ stays as correct as one that remakes all the time; it only grows. A remake does
thing: nothing is written at a history from before its base, so what a node taken off
its list could still commit there ends with it.
-A remake that races a version or a listing leaves the nodes that took it where they
-are, apart from those that switched, until their operators move them or a fork. A node
-with an empty document can't check: it takes the epoch its peers give it, or the one
-its operator pins.
+A remake that races a version or a listing leaves the nodes that took it where they are,
+apart from those that switched, until their operators move them or a fork. An operator
+moves a node that took a version by having it drop that version (Changing the policy):
+the base then holds the version it reads, so it switches, and the new epoch writes the
+version again from the votes replayed, as a node writes any it holds passed. A node with
+an empty document can't check: it takes the epoch its peers give it, or the one its
+operator pins.
### Where Automerge sets limits