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/swarm/refusals.rs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'src/swarm/refusals.rs') diff --git a/src/swarm/refusals.rs b/src/swarm/refusals.rs index 30c3971..652f9bc 100644 --- a/src/swarm/refusals.rs +++ b/src/swarm/refusals.rs @@ -12,8 +12,7 @@ //! everything built on it: its document as it would be without them, its own writes //! among them quarantined, the others' listed as refused (`AppState::drop_taken`); one //! taking much, once a second member says so too. If its rules take it, the two -//! policies disagree, which it logs; finding out which is right is left -//! (`future-work.md`, Write protection by checking changes). +//! policies disagree, which it logs; it doesn't find out which is right. use std::time::Duration; -- cgit v1.3.1