aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 04:14:07 +0000
committertv <tv@krebsco.de>2026-11-16 04:14:07 +0000
commit37ddd429652f5a8764c6035078b4e4e3bd663714 (patch)
treed69d9b7c501af76a257a15d9dce31fb24c5e14a4 /docs/federation.md
parent88536531e309d7ba2f8ebaa82431618f617347fe (diff)
federation: a member at a remake's base is a node its party lists there
A node follows a remake only where it is a member at the base: listed there, or listed and registered, the design didn't say. Listed: a node its party listed registers in the new epoch as it would have in the old.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md19
1 files changed, 10 insertions, 9 deletions
diff --git a/docs/federation.md b/docs/federation.md
index e83cefe..d8ffc46 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -480,15 +480,16 @@ snapshot is a function of its base. 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
against the committed epoch *(checked: `remake::switch`)*, from a base it holds, where
- it is a member and the version it reads is written, as it reads it when it switches: a
- version it takes while it builds leaves it where it is, as one taken before. Never on
- its peers' word, however it hears of the new epoch: a node that lacks some of the base
- (it was away) syncs it from peers that keep the old epoch, each change judged there,
- and builds then; where it can't build it, it stays where it is, says so, and never
- rejoins an epoch it refused. A remake's decision is its coordinator's alone, and so is
- its abort: whether one expired is no node's to say, and one its coordinator leaves
- undecided binds nobody. How long a node keeps the old document is its own setting,
- not the remake's, and while it keeps it, it syncs it with nodes still on that epoch.
+ it is a member (its party lists it there) and the version it reads is written, as it
+ reads it when it switches: a version it takes while it builds leaves it where it is,
+ as one taken before. Never on its peers' word, however it hears of the new epoch: a
+ node that lacks some of the base (it was away) syncs it from peers that keep the old
+ epoch, each change judged there, and builds then; where it can't build it, it stays
+ where it is, says so, and never rejoins an epoch it refused. A remake's decision is
+ its coordinator's alone, and so is its abort: whether one expired is no node's to say,
+ and one its coordinator leaves undecided binds nobody. How long a node keeps the old
+ document is its own setting, not the remake's, and while it keeps it, it syncs it with
+ nodes still on that epoch.
* **Two decisions for one epoch** come from a coordinator that wrote two, or from
remakes decided at once. A node that holds both follows neither, says so, and leaves
it to its operator. On its operator's word, a node builds the remake named of the