diff options
| author | tv <tv@krebsco.de> | 2026-11-16 13:12:14 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 15:05:55 +0100 |
| commit | 56eafff2d109633042e5b56ec8d695989d81eeee (patch) | |
| tree | 74e5bef1968eb80a1b8230725b0e6e1f591c39bb /src/main.rs | |
| parent | 4bcb412f95a003d86a0bbad64576259a951e7c80 (diff) | |
docs/federation: the design on the store
The federation is the store's fold. What a party signs is an event: a JCS object naming
its dependencies, signed with an SSH signature by one of its party's keys, or by nobody
for a federation's root, a fork's and a version. An event names no swarm, no version
and no place in the document: its history says which store it is in and which version
it is written under.
A place is a path a rule matches, its value the latest write its party signed there
that counts: one that no other counting write there has in its history, and of several
the one with the lowest ID. Key sets and node lists are read the same way. A vote,
proposal, key set and node list is an event of its own kind, a passed proposal takes
effect by a version event, and a node takes a version only where it changes the one it
reads, as before.
A fork is a store whose root builds on the heads it forks at, carrying their history,
so that any node checks it from its events alone. What carries the store, its document
and its remakes, the federation leaves to `docs/store.md`, with the promises and attacks
about them; the attacks left are numbered anew.
Diffstat (limited to 'src/main.rs')
0 files changed, 0 insertions, 0 deletions
