From 00d6446feab420c8c3b0c31d45d1b986120d56c9 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 06:21:49 +0100 Subject: [PATCH] Design 47 H: H-A-128, nats_consumer_remove judges a module's durable by prefix Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 5 +++++ 1 file changed, 5 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 f09692cb..f4609ba4 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 @@ -563,3 +563,8 @@ Where two preparers disagreed, the chosen one is named. orphan and goes. The judgement is by name, not by stream (H-A-126). (2) `why` is the warrant: the tool acts at once and writes the hand act through mesh-hand-acts as `nats_bucket_expiry` does. The clean state runs at the operator's terminal, so an ask of the operator would answer the operator's own call (P7). P4, P7. +- **H-A-128 (`nats_consumer_remove`: the name rule is a prefix, 06:24)** H-A-127's rule is read as a prefix: a durable + is a module's when its name is `_` or begins with `__` for a module of an accepted + manifest on any node (the keeper's accepted set holds modules, not nodes; the developer's reading of 06:23), since a + module may name more than one durable with a suffix. The tool refuses those and removes every other. P3 (a wrong + removal of a live consumer is a silent failure), P4.