aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 03:13:07 +0000
committertv <tv@krebsco.de>2026-11-16 03:13:07 +0000
commit61a13f5ba52afcb6bec3534b8d016708c1581a4e (patch)
tree5cca7d639467a095e1cf2dfdf8cb8fb174811376
parent677dd5efd58796212839a43e87555746f9b21abb (diff)
federation: stage work for screening and a new node's party
Screening judges a batch at a frontier that every change touching what the rules read moves, or a later change of the batch is judged at heads it doesn't hold: stage 1 moves it for what the federation reads too. And a node syncs with members only, but is one only once its own entry names its party: stage 3 shows the party in the handshake before that.
-rw-r--r--docs/federation.md23
1 files changed, 13 insertions, 10 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 22cae30..7e6d7d3 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -734,18 +734,21 @@ On a federated swarm:
1. **The federated policy**: a swarm started federated by its genesis change, with the
key sets and node lists its first version sets; versions and what makes one valid,
rules and paths, values in `@` keys, keys, votes, passing and dead, which version a
- node takes and the current one, judging by it; votes and proposals by their
- version's keys; the protocol data as listed, all else closed; the `cv3.` envelope
- with the meta's version, and the order by it; node lists, a node's party in its
- configuration, and tokens from one's own party's nodes only; what every reading of a
- strict policy in continuum (`strict()`) makes of the federated one; the byte formats
- (a version's JCS bytes, hashes in paths and how two compare, the envelopes a version
- sets, the meta's version). A node that doesn't know the policy stops taking changes.
- Until stage 4, a federated swarm takes no remake.
+ node takes and the current one, judging by it; votes and proposals by their version's
+ keys; the protocol data as listed, all else closed; the `cv3.` envelope with the
+ meta's version, and the order by it; node lists, a node's party in its configuration,
+ and tokens from one's own party's nodes only; what every reading of a strict policy
+ in continuum (`strict()`) makes of the federated one; screening's frontier moved by
+ every change touching what the federation reads (versions, proposals, votes, key
+ sets, node lists), as `access::screen` moves it today for what continuum's rules
+ read; the byte formats (a version's JCS bytes, hashes in paths and how two compare,
+ the envelopes a version sets, the meta's version). A node that doesn't know the
+ policy stops taking changes. Until stage 4, a federated swarm takes no remake.
2. **What counts**, read by the current version and the keys; shown in the API.
Reports of a party that voted twice, and of versions a node refused.
-3. **Nodes**: membership by the node lists and the party a node's own entry names, a
- node syncing with members only (a wire change), neighbours by party.
+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
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.