aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md18
1 files changed, 11 insertions, 7 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 8700e45..f1229b0 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -1,12 +1,16 @@
# Federation: a design
-A design, built stage by stage (Stages): so far, the store it builds on, held in memory,
-and the federation as its fold (`federation::fold`), with the byte formats. It says how
-a swarm can be kept by parties that don't trust each other, for a first use: the krebs
-registry ([krebs/kartei](https://github.com/krebs/kartei)), today plain files in a git
-repository that one maintainer merges into. What it is for is narrow: to hand out
-identifiers (names, addresses, keys), and to give every party a namespace of its own
-that everyone reads.
+A design, built stage by stage (Stages): so far, the store it builds on, held in memory
+and in a swarm's document, members by the federation and the store at a node's API, as
+[`store.md`](store.md) says; the federation as its fold (`federation::fold`), with the
+byte formats; and a party's client (`continuum-party`, `federation::client`), which
+signs its party's events, votes by its record, signs again what a move refused, and
+names a party that voted twice. It says how a swarm can be kept by parties that don't
+trust each other, for a first use: the krebs registry
+([krebs/kartei](https://github.com/krebs/kartei)), today plain files in a git repository
+that one maintainer merges into. What it is for is narrow: to hand out identifiers
+(names, addresses, keys), and to give every party a namespace of its own that everyone
+reads.
It asks as little as it can of continuum and promises the least that makes a federation
possible. A federation that cooperates settles fast; one that doesn't comes apart, and