From 84366037195819741f464b8e2539787d68ff2d72 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 17:24:36 +0100 Subject: [PATCH] Design 47 H: H-A-160, every re-serve keeps unchanged subscriptions --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 897658fc..eed823e3 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -807,3 +807,9 @@ Where two preparers disagreed, the chosen one is named. versions of its own (G §348, §349, §369; §372 removes the state): its own numbering goes, with the floor wait and the publish-unanswered bound of that state, and a registry's published whose digest is not that of a kept entry leaves the entry as it is. The reservation is the one place a version is numbered and published. P7, P3. +- **H-A-160 (every re-serve of a module's tools keeps its unchanged subscriptions, 17:24)** Met in the build + of H-A-158: the runner re-serves a module's tools not only on a membership but also when a ledger binding is added + or removed (its repairs), stopping every subscription first, so a call is lost there the same way. H-A-158 holds + for every re-serve: one serving routine owns a module's subscriptions, keeps those whose subject and queue are + unchanged, adds the new, then stops the ones no longer named, so no subject is ever served twice or not at all. + P3, P7.