From 8f6ec848b01fa692b09ae8aae25d383d281eb996 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 17:10:41 +0000 Subject: federation: groups that parted come together as parties come in, not by merges A merge, a fork at heads of several stores, named every party's keys anew, so that a party wrote its key set again before anything a key of its set signed counted there; and kept each side's values side by side, so that a value a party replaced on one side came back where the other side's write had the lower ID. Letting the other side's parties in, by a version or a fork naming them, who sign again what they keep as a party's client signs again what a move refused, does the same with nothing new. So a fork is at heads of one store: the fold makes its root from that store's state, and the store from its own heads (`Store::fork`). Merges' rows go, those after them move up, and Roads not taken says why, with merging in place. --- docs/federation-tests.md | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) (limited to 'docs/federation-tests.md') diff --git a/docs/federation-tests.md b/docs/federation-tests.md index 4ab3f64..104df96 100644 --- a/docs/federation-tests.md +++ b/docs/federation-tests.md @@ -30,9 +30,9 @@ are. * **Keys.** Ed25519 keys made from seeds, signing as `ssh-keygen -Y sign` does; a vector checks one signature against `ssh-keygen` itself. * **Events.** A builder for every kind (writes, key sets, node lists, proposals, votes, - version events, checkpoints, roots, forks and merges), each from a party, a key and - its dependencies, encoded and signed as the design says; and for what is none: bytes - that aren't JCS, a field missing or more, another key, a broken signature, too large. + version events, checkpoints, roots and forks), each from a party, a key and its + dependencies, encoded and signed as the design says; and for what is none: bytes that + aren't JCS, a field missing or more, another key, a broken signature, too large. * **Scenarios.** A scenario is a value: the parties and the first version, events by name with their dependencies, which node is given which events in which order, and what is expected (each node's verdicts, the current version, what counts, the @@ -50,7 +50,7 @@ are. passing and dead, for every number of parties from 1 to 20; one yes at a time; which version a node takes, and the current one; a party's keys and node list by their `since`; a place's value; rules matching (`{party}`, `*`, `**`, first match); what - counts, item by item; checkpoints and what they keep; forks and merges. + counts, item by item; checkpoints and what they keep; forks. * **The attacks marked unit**, each by a scenario, its expectation the row's. * **The store** with a fold made for its tests, smaller than the federation's, for what `store.md` checks (Tests): order, history, refusal, checkpoints. @@ -79,10 +79,8 @@ each after its dependencies), and for seeded histories and orders beyond that. judging it with the whole history gives; reading gives what the whole history reads but for what counted no more; nodes moving at different times read the same once they hold the same; moving refuses nothing that decided it. -8. **Forks and merges.** A fork takes nothing of the stores it came from after its - heads, nor they of it; a merge's state is the values that count on each side at - places its version gives their party, and a key dropped on one side brings back - nothing until its party lists it again. +8. **Forks.** A fork takes nothing of the store it came from after its heads, nor that + store of it; and its root keeps what counts at its heads with its version current. 9. **Votes a node casts by itself.** By its rules a node casts one yes at a time, never `true` and `false` on one proposal, and, by a rule for checkpoints, backs nothing that changes more. @@ -113,9 +111,9 @@ each row marked sim expects. ## Fixed bytes Vectors for: an event and its ID, a signature, a version and its hash, a checkpoint and -its ID, the genesis change of a federation's root, of a fork's and of a merge's, and a -snapshot after a checkpoint. A vector that changes is a change of the federation, which -takes its next number ([`federation.md`](federation.md), Changing the federation). +its ID, the genesis change of a federation's root and of a fork's, and a snapshot after +a checkpoint. A vector that changes is a change of the federation, which takes its next +number ([`federation.md`](federation.md), Changing the federation). ## Fuzzing and mutants @@ -144,7 +142,7 @@ takes its next number ([`federation.md`](federation.md), Changing the federation 3. **The store on Automerge**: the same as in memory, changes that stay sound, the store's attacks marked unit, the simulations of a federation without forks or remakes, the vectors of genesis changes. -4. **Forks**, merges among them: their rows, properties and vectors. +4. **Forks**: their rows, properties and vectors. 5. **Remakes**: their rows and simulations, and the vector of a snapshot after a checkpoint. 6. **The registry**: its rules by example, and the tools reading and writing kartei. -- cgit v1.3.1