aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 12:48:29 +0000
committertv <tv@krebsco.de>2026-11-18 13:59:42 +0100
commitd130c0612b4c63f2d30da65ebcc231018c1f2606 (patch)
tree8700f2d53351cbbecbe772ea7701bf6240d5210c /docs/access.md
parent0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (diff)
docs: references to another document's section linked to it
Where a document names a section of another after linking to it ("([`store.md`](store.md), Pinned checkpoints)"), the name links to that section too, by the id both GitHub and cgit's about filter give its heading; paragraphs that grew past the width are wrapped anew, links and code kept on one line each.
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md31
1 files changed, 16 insertions, 15 deletions
diff --git a/docs/access.md b/docs/access.md
index 7c6c7e6..019565e 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -120,7 +120,7 @@ curl -H "Authorization: Bearer ct1.…" http://other-node:3000/store
* **Who signs it**: the node it logged in on, with its node key. Every node takes a
token signed by a member of the swarm (the member list gives the keys: a node ID is
its key), and none signed by another or since forgotten; in a swarm holding a store
- ([`store.md`](store.md), Members), only one it signed itself.
+ ([`store.md`](store.md), [Members](store.md#members)), only one it signed itself.
* **What it says**: who, how it proved it, when it ends, and optionally less than the
user may do (`limit`, capabilities as `POST /admin/users/{name}` takes them): never
what the user may do. Every node judges a request by the registry it holds then, so
@@ -310,12 +310,13 @@ through (they look at the path asked for, the rules at everything the change doe
can't cut its node off.
With `"signatures": "required"`, a change also needs a signature by the node it names
-([`api.md`](api.md), Signed changes): every node then signs what it sends, so every
-change leaves vouched for, and one no signature vouches for yet waits, with whatever builds on it, until one does
-(they come with the changes, in the same sync messages). A signature vouches for
-its change and the node's changes it builds on, no others: a change made under another
-node's actor is forged, refused, and logged as its sender's (`A peer brought changes
-forged`). A member can then no longer write as another member; the user a change names is still its node's word.
+([`api.md`](api.md), [Signed changes](api.md#signed-changes)): every node then signs what
+it sends, so every change leaves vouched for, and one no signature vouches for yet waits,
+with whatever builds on it, until one does (they come with the changes, in the same sync
+messages). A signature vouches for its change and the node's changes it builds on, no
+others: a change made under another node's actor is forged, refused, and logged as its
+sender's (`A peer brought changes forged`). A member can then no longer write as another
+member; the user a change names is still its node's word.
Whatever the policy, and without one, a change is refused that Automerge itself
wouldn't have written: bytes that aren't Automerge's encoding of the change; a first
@@ -468,14 +469,14 @@ Under a strict policy, the same, as part of bob's entry, signed (`continuum-sign
_continuum/users/bob '{…}'`).
A node takes one only from that user, for that path, replacing what is there, by one of
-the user's keys, and if the user may write there ([`api.md`](api.md), Signed values); it
-writes nothing else there, nor within or above such a value (`409`), and the users API
-changes nothing (`409`). A swarm turns strict only at its start (`--bootstrap-policy`,
-[A new swarm](#a-new-swarm), above) or through a remake
-([Turning a swarm strict](#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 strict only where its `values` is a string, as continuum
+the user's keys, and if the user may write there ([`api.md`](api.md),
+[Signed values](api.md#signed-values)); it writes nothing else there, nor within or above
+such a value (`409`), and the users API changes nothing (`409`). A swarm turns strict only
+at its start (`--bootstrap-policy`, [A new swarm](#a-new-swarm), above) or through a
+remake ([Turning a swarm strict](#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 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