From 86e510f96659b3eb8c21de88107fd7b86cdde902 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 04:24:52 +0000 Subject: corpus: cases chosen by what they show, merges by nodes their party lists The corpora written from four seeds of each kind showed little: of 32 histories, 4 versions written, no move and no stop, and every merge event refused, as the generator signed them with any of ten node keys, so the corpus of revision 1 judged as the base revision's did. A generated merge event is signed by a node its party lists there, more often than not. Of each kind, the corpus keeps the histories of the first two seeds, and of the next 400 those showing what the ones kept don't (`shows`: of each kind of event, what became of one; a version written, a move, a stop), eight at most. The check asks that together a revision's cases show a version written, a move to a checkpoint, a stop, and a merge event taken where the revision has merge events, else refused. --- docs/federation-tests.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/federation-tests.md b/docs/federation-tests.md index a39e749..c22f300 100644 --- a/docs/federation-tests.md +++ b/docs/federation-tests.md @@ -128,9 +128,13 @@ every node must agree on ([`federation.md`](federation.md), What each revision takes, refuses and reads, as fixed bytes: for each revision this continuum knows, a file in `src/federation/corpus/` of histories generated at that -revision (of every kind the properties generate, a few seeds each), each event's bytes -with what became of it, by kind (taken, refused and why, by kind, waiting, held back, gone -with a move), and what the store reads after. A revision's file is written once, as the +revision (of every kind the properties generate, those of the first two seeds, and of the +next few hundred those showing what the ones kept don't: of each kind of event, what +became of one, a version written, a move, a stop; eight at most), each event's bytes with +what became of it, by kind (taken, refused and why, by kind, waiting, held back, gone with +a move), and what the store reads after. Together they show a version written, a move to +a checkpoint, a stop, and a merge event taken where the revision has merge events, else +refused. A revision's file is written once, as the revision is made (`write_the_corpus`, run by hand), and never edited after: every later continuum judges it alike (`every_revision_judges_as_its_corpus_says`), so that a change to judging that alters an earlier revision's comes as a later revision. Its first line -- cgit v1.3.1