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. --- src/access/mod.rs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'src/access/mod.rs') diff --git a/src/access/mod.rs b/src/access/mod.rs index f3e5f80..e223756 100644 --- a/src/access/mod.rs +++ b/src/access/mod.rs @@ -68,8 +68,7 @@ pub(crate) struct Capability { /// nothing here. pub(crate) rights: BTreeSet, /// Who granted it: a user (`user:`), or for those the genesis node records, the - /// node (its node ID). Kept so that granting on, by delegation, can come later - /// without a new format (`future-work.md`, Authentication across nodes). + /// node (its node ID), kept with the capability. #[serde(default)] pub(crate) by: String, /// When it was granted (Unix ms). -- cgit v1.3.1