diff options
| author | tv <tv@krebsco.de> | 2026-11-19 04:02:52 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 05:13:51 +0100 |
| commit | 2c9d42ed955705a0207b047918f58ef258dcfa4f (patch) | |
| tree | b8d50ee2fdce459a4b61fff4e8bddff6d308da8e /docs/dashboard.md | |
| parent | 0d2467e15ec0c9c035b1074a2dd4eece6b24c599 (diff) | |
federation: a corpus per revision, judged alike by every later continuum
Nothing checked that judging under a revision stays what it was: a change to the fold
that alters what an earlier revision takes, refuses or reads parts nodes running it from
nodes that don't, and the tests regenerate their expectations with the code.
For each revision this continuum knows, a file in `src/federation/corpus/` holds
histories generated at that revision, of every kind the properties generate, each event's
bytes with what became of it, by kind and never by a refusal's words, and what the store
reads after; its first line names the revision by its ID. It is written once, as the
revision is made (`write_the_corpus`, an ignored test run by hand), and never edited
after; every later continuum judges it alike (`every_revision_judges_as_its_corpus_says`),
which fails where a revision has no corpus yet, saying how to write it.
The test plan describes it.
Diffstat (limited to 'docs/dashboard.md')
0 files changed, 0 insertions, 0 deletions
