From 3bf93bc192bf362b58b2161ac05da0bb8323bf43 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 9 Nov 2026 17:33:24 +0000 Subject: docs: what is postponed or rejected stays in its own two files Docs and comments outside future-work.md and review-rejections.md say what the code does, and point nowhere else for what it doesn't: the architecture page's map, the transports' forwarders, keys with `/`, a strict swarm's registry, trust.md's "Not yet" (now saying what isn't protected, in a sentence), the topology bench, and the comments of the change benchmarks, capabilities' grantor, tokens, dissemination, refusals and topology. --- docs/access.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'docs/access.md') diff --git a/docs/access.md b/docs/access.md index 7bacd91..1397656 100644 --- a/docs/access.md +++ b/docs/access.md @@ -468,8 +468,7 @@ kind, which its proposal and its snapshot's metadata say: a majority of members labelling it otherwise (`compact`, its snapshot holding the registry it wants) gets it followed, as nodes whose own build differs take the quorum's snapshot. So a strict swarm's registry, policy and bans change by its users' signatures against a minority of -members, not against a majority ([`trust.md`](trust.md); comparing a downloaded snapshot -with the node's own build is in [`future-work.md`](future-work.md)). Compaction +members, not against a majority ([`trust.md`](trust.md)). Compaction that keeps, at the places values are signed (the registry, `_continuum/access`, the bans, the paths listed in `userSigned`), only the values an operator looked over and signed, and sets the strict policy. What was written after its base reaches the new -- cgit v1.3.1