From 3fccc4f6859cf0b4d93e7d166142e1ab9255723f Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 19:38:26 +0000 Subject: access: what a change of a swarm holding a store writes Every node judges a change of a swarm holding a store by what it writes, at its history (`docs/store.md`, What a change writes), in place of rules by path: `access::holding`. It writes events, each at `_continuum/events/` the bytes whose SHA-256 that is, no larger than the fold allows (the federation's 256 KiB), at a key held nowhere at the change's history; and its node's entry, with the member list's map where there is none. Everything else is refused, as closed: values outside `_continuum`, the policy, the swarm's ID, users, bans, the topology, remakes and their acks. Nothing deletes or replaces an event. A change names its node; the genesis change's writer names none, so no change under it is taken but the genesis change. In a swarm not holding a store, a change writing a policy naming one is refused: a swarm holds a store from its genesis change, or not at all. The inspector tells a put of bytes apart (`Action::PutBytes`), with the bytes, for the events' check. All of it behind the `federation` feature. --- src/access/mod.rs | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/access/mod.rs') diff --git a/src/access/mod.rs b/src/access/mod.rs index cc6b7a2..65c3817 100644 --- a/src/access/mod.rs +++ b/src/access/mod.rs @@ -17,6 +17,8 @@ use crate::document::meta; pub(crate) mod bans; pub(crate) mod challenge; pub(crate) mod envelope; +#[cfg(feature = "federation")] +pub(crate) mod holding; pub(crate) mod policy; pub(crate) mod registry; pub(crate) mod rules; -- cgit v1.3.1