aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 02:10:47 +0000
committertv <tv@krebsco.de>2026-11-16 02:10:47 +0000
commit0afc17ab0c6e0e34ce63c33db736e4fe59305c12 (patch)
treec125c4b128201346d089bd5aab48238f7d24dff9 /docs/access.md
parentb606449e51b8233d214f14500e0e47cd42af5744 (diff)
policy: strict only where its values is a string
The policy was read in typed JSON, so that an Automerge text spelling "signed" at its `values`, which no operation `rules::turns_strict` asks of writes, turns no swarm strict. But that read every policy anew: a setting that wasn't a string, or a text at `signatures`, made a policy no node knows in swarms that aren't strict, which read it as before. The policy is read in plain JSON again, as it was, and only its strictness asks more (`policy::of`): it reads strict only where its `values` is a string in typed JSON, an envelope read as its payload. A policy that would read strict only through a text, at `values` or holding the policy, is one no node knows. Every policy that doesn't read strict reads as it did.
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/access.md b/docs/access.md
index a85a3e5..dcd67f8 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -469,9 +469,9 @@ changes nothing (`409`). A swarm turns strict only at its start (`--bootstrap-po
new swarm, above) or through a remake (Turning a swarm strict, below), which keeps only
what an operator looked over: each is its epoch's first change, so no change of a strict
epoch is from before its policy. A change writing a strict policy where the policy isn't
-strict is refused; and a policy reads only as continuum writes it, plain JSON or an
-envelope: a text, or a setting that isn't a string, makes it one no node knows, never
-what its characters spell. A strict swarm stays strict: its policy is written again only
+strict is refused; and a policy reads strict only where its `values` is a string, as
+continuum writes it: one that would read strict only through an Automerge text is one no
+node knows, never what its characters spell. A strict swarm stays strict: its policy is written again only
as strict, never relaxed nor deleted, nor moved to a policy its nodes don't know (a node
that doesn't know a policy reads it as none it can judge by); to leave it, start a new
swarm from its content (A new swarm, above). A value there that isn't an envelope starts