From 79614926332977718956f35e1adf80ae67e219f1 Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 20:08:28 +0000 Subject: store: a stopped node leaves out none of what it holds back A store that stopped can't tell which of what it holds back will be taken, nor which of what waits: `Store::held_back` gives both, each after what it builds on. A node leaves out none of it: it puts it again where its document lacks it (`Holding::lacking`), a remake's snapshot holds it (`Holding::at_base`), and after a switch or a rejoin it puts again what of it the document it left held (`Holding::left`). A remake while nodes are stopped no longer drops what was put since the stop, nor the event they stopped at. Tested: a node keeps what it holds back, what waited among it, through a snapshot, and a store read anew from that stops there again; and a simulation: a swarm stopped at a version compacts, a node away meanwhile rejoins and one started again with nothing reads the new epoch, each stopping there, holding back what came after, until their operators have them drop that event. --- docs/federation.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index a179846..ae010fb 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -813,9 +813,10 @@ moves to it by a version of its policy that names it (`"federation": 2`), which parties pass once their nodes run a continuum that knows it. A node that doesn't know the federation its swarm's root names holds no store, and says so. One that doesn't read a version that passed on the version it reads stops at the version event writing it, and -says so: it takes nothing and refuses nothing from then on, and keeps none of it across a -restart, until it runs a continuum that reads it, or its operator has it drop that event -([`store.md`](store.md), [A node's own](store.md#a-nodes-own)). Dropped, the node refuses +says so: it takes nothing and refuses nothing from then on, leaving out none of it, a +remake's snapshot neither, and keeps none of it across a restart, until it runs a +continuum that reads it, or its operator has it drop that event ([`store.md`](store.md), +[A node's own](store.md#a-nodes-own)). Dropped, the node refuses that event and any writing that version, as any version its operator had it drop, and goes on under the version before. One beside the version it reads, it refuses of its own, as any other ([Changing the policy](#changing-the-policy)). -- cgit v1.3.1