aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-15 23:34:11 +0000
committertv <tv@krebsco.de>2026-11-15 23:34:11 +0000
commit3827195e784999c772357e547d3d4efc9bb8d627 (patch)
tree0f0806ee290bfb779b5dcf15c9936f44da3b75d2 /docs/access.md
parentcc998c1d45939d170bcf8a6512817405ed2b44a3 (diff)
policy: read only as continuum writes it
A swarm turns strict only at its start or through a strict remake, and a change writing a strict policy where the policy isn't strict is refused, found by its operations: `"signed"` put at the policy's `values`, or an envelope asking for it put at its place. But the policy was read in plain JSON, where an Automerge text reads as a string, and writing a text is no such operation: `{"$text": "signed"}` at `values`, through the typed API, turned a swarm strict that nothing refused, with a time before it nothing closes. The policy is read in typed JSON now (`store::read_plain_as`): what continuum writes there reads as it is, plain JSON or an envelope, and a text, a counter or bytes as itself, tagged; a setting that isn't a string makes a policy no node knows (`policy::read`), as a version it doesn't know does. So no text turns a swarm strict, and the operations `rules::turns_strict` asks of are the only ways to. A policy holding none of these reads as before.
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md13
1 files changed, 8 insertions, 5 deletions
diff --git a/docs/access.md b/docs/access.md
index 942621c..a85a3e5 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -469,12 +469,15 @@ 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. 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
+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
+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 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.
+swarm from its content (A new swarm, above). 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.
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