aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 12:46:42 +0000
committertv <tv@krebsco.de>2026-11-19 13:52:29 +0100
commit03105d40322dff9c18f0571872ab0f643aded0f7 (patch)
treea96b625f4d57d23ee12a6db72780446530b413cd /docs/federation.md
parente8f0760a9b08e6b1a7372e79c48744035d1e4e1a (diff)
federation: checked against the release a federation-<F>.<R> tag namesfederation-1.1
A corpus of generated histories, committed, said what this code made of them, right or not, and held hundreds of kilobytes a revision; generated from code that changes, it could only be checked, never written again. Each release that makes a revision is tagged `federation-<F>.<R>`, the federation's number and the revision's (`federation-1.1`, revision 1 of federation 1). `scripts/federation-check` writes histories from this tree (`write_histories`, an ignored test): of each revision it knows and each kind the properties generate, those of a few seeds from a random one it says, and the attack tests' crafted ones, as each test offered them where nothing but offers made them. It judges them with `continuum-party judge` here and with the continuum the latest such tag names (or one given), built in a worktree and kept between runs, leaves out those whose root the tagged one reads as none, and says where the two differ. Run before a release, not by `cargo quick`. The corpus and its test are gone; the test plan and `federation.md` say how a release is checked.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 30bff6e..8dc23b3 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -881,10 +881,13 @@ version names: a change there splits the swarm until every node runs it
A version leaves `revision` out for the base revision, and names a revision no earlier
than that of the version it changes. What a revision adds counts at a history only where
the version current there names that revision or a later one: before, every node judges
-as before, so that what a party uses early, every node refuses alike. A version is read by
-the revision it names, so one moving to a revision may already hold what that revision
-adds to a version; its proposal, the votes on it and its version event are judged under
-the version before. A node voting by itself backs no version changing the revision
+as before, so that what a party uses early, every node refuses alike. A release making a
+revision is tagged `federation-<F>.<R>`, and every later one is checked to judge as it
+does under the revisions it knows ([`federation-tests.md`](federation-tests.md),
+[Against released revisions](federation-tests.md#against-released-revisions)). A version
+is read by the revision it names, so one moving to a revision may already hold what that
+revision adds to a version; its proposal, the votes on it and its version event are judged
+under the version before. A node voting by itself backs no version changing the revision
([Votes a node casts by itself](#votes-a-node-casts-by-itself)): its party's operators
vote on it.