aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/access.md b/docs/access.md
index 89e74d7..b2cdb70 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -470,7 +470,11 @@ that isn't strict, a member may write as any user). So a swarm is best strict fr
start (`--bootstrap-policy`, A new swarm, above); one already running turns strict
through a remake (Turning a swarm strict, below), which keeps only what an operator
looked over. Writing the strict policy into it directly trusts it as it is: look it
-over first (`continuum-signed verify` on each entry). A value there that isn't an envelope
+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 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.