From 842071859a532bd85759ebd6801594f64bb0da0d Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 23:14:41 +0100 Subject: [PATCH] Answer A-410: a running module the node cannot fingerprint is held, never counted as removed --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index d6402843..56fbba76 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -981,3 +981,10 @@ the principle that settles it, cited as "design 47 G A-n". is the seat event's subject with each `<...>` token as `*` (a trailing one also as the rest); a consume naming a seat that says no such event is refused aloud by the grants part, never turned into a module's event. The indexer's `catalog-revision` duplicate id names the branch, and it is published with the bus's acknowledgement. +- **A-410** (live, the control-node 2026-11-14 about 22:55: proposals placing the pipeline were answered "differs", with + fail2ban, pacman and mesh-mail-reader counted as removed, while all three run and their assignments hold them; a module + started before the node-engine wrote fingerprints has none in what it runs, and none can be made for it, so its + comparison is skipped, and a skipped comparison was counted as a removal; principles 2 and 3) A module the node runs + whose fingerprint it cannot read or make is held: it is kept as it runs and said as held, with why, in the node's + answer, never counted as removed and never stopped for it. Only a module the node runs that no assignment names is + removed.