From 03105d40322dff9c18f0571872ab0f643aded0f7 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 12:46:42 +0000 Subject: federation: checked against the release a federation-. tag names 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-.`, 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. --- docs/federation.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'docs/federation.md') 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-.`, 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. -- cgit v1.3.1