aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/federation-tests.md4
-rw-r--r--docs/federation.md7
2 files changed, 6 insertions, 5 deletions
diff --git a/docs/federation-tests.md b/docs/federation-tests.md
index bc91fad..4b627ac 100644
--- a/docs/federation-tests.md
+++ b/docs/federation-tests.md
@@ -1,8 +1,8 @@
# Testing the store and the federation: a plan
A plan, built stage by stage (By stage): so far, the store's tests, the federation's
-fold's, the store's on Automerge, the forks', and the remakes' (stages 1 to 5). It says
-how the store ([`store.md`](store.md)) and the federation
+fold's, the store's on Automerge, the forks', the remakes', and the registry's (stages 1
+to 6). It says how the store ([`store.md`](store.md)) and the federation
([`federation.md`](federation.md)) are tested, so that nothing in continuum breaks the
federation, and no change made later breaks it apart. It is the contract the code is
built to: a stage is done when its tests are.
diff --git a/docs/federation.md b/docs/federation.md
index 1c59995..beb603d 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -5,10 +5,11 @@ and in a swarm's document, members by the federation and the store at a node's A
[`store.md`](store.md) says; the federation as its fold (`federation::fold`), with the
byte formats; 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; and votes a node casts by itself (`federation::vote`), following
+party that voted twice; votes a node casts by itself (`federation::vote`), following
parties and proposing checkpoints, which back a checkpoint by the voters' rule, and
-through which its party votes by hand. It says how a swarm can be kept by parties that
-don't trust each other, for a first use: the krebs registry
+through which its party votes by hand; and the registry on it (`federation::registry`,
+`continuum-party kartei`). 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