aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md15
1 files changed, 10 insertions, 5 deletions
diff --git a/docs/access.md b/docs/access.md
index b64bd21..c4ce295 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -472,12 +472,17 @@ through a remake (Turning a swarm strict, below), which keeps only what an opera
looked over. Writing the strict policy into it directly trusts it as it is: look it
over first (`continuum-signed verify` on each entry). From then on nothing is added to
the time before: a change written under a policy that isn't strict is refused, received
-or held, unless it is in the history of the change that wrote the strict policy, so a
-member can't plant at that time what nobody could follow; a node that took one beside
-that change drops it once a peer tells it so (Changes judged on every node, below). A
+or held, where the change that turned the swarm strict (that wrote the strict policy
+under one that wasn't) is neither in its history nor built on it, so a member can't
+plant at that time what nobody could follow; a node that took one beside that change
+drops it once a peer tells it so (Changes judged on every node, below). The policy
+written again later doesn't change which change that is. One written beside it is
+refused like any other, even one turning the swarm strict too, so a change made later
+to look as old can't take its place: two members turning a swarm strict at once split
+the nodes that took one from those that took the other, so it is turned from one. A
value there that isn't an envelope starts its chain anew: any envelope its user once
-signed for that path replacing nothing (`prev` empty) can be put there again. Without the policy, signed values may
-be written all the same, and plain ones too.
+signed for that path replacing nothing (`prev` empty) can be put there again. Without
+the policy, signed values may be written all the same, and plain ones too.
Keep two users who may manage users, or two keys each: under a strict policy, a
registry whose only manager lost its keys changes no more (the protocol writers do