From f0559b3a71f6ef5c72c747f96f00e763249a6a2d Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 06:12:22 +0100 Subject: [PATCH] Design 47 H: H-A-126, the bus module's drop tools exist; H-A-121 (1) withdrawn Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 9 +++++++++ 1 file changed, 9 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 a514e51e..79569618 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 @@ -548,3 +548,12 @@ Where two preparers disagreed, the chosen one is named. owns (P9: a module's state is read through its owner's view, never copied); a pipelines block belongs in the status view and is parked as an idea, not built in H1. Told to the operator as a change of what they see: the knowledge base's overview page no longer shows deliveries. P9, P5. +- **H-A-126 (the bus module's drop tools exist; H-A-121 (1) withdrawn, 06:12)** No new tool: the bus module already + serves them (the developer's reading of 06:11). A retired state bucket (the gate's `merges`, a seat's `asks` and + `turns`, mesh-config's `pulls`, the indexer's `pending`) is kept data no accepted manifest asks for once H1's + manifests are taken in, so the keeper's `nats_drop` drops it, by warrant, after its snapshot, as today. The source + bucket's old keys go by `nats_bucket_remove` with the prefix, before `gate_source_seed`. A durable consumer goes by + `nats_consumer_remove`; it refuses only a consumer an accepted manifest asks for, and no longer every consumer of a + kept-data stream: one no manifest names is an orphan on that stream, removed by warrant (`why` required) and + written in the hand-act log as the keeper's requests are. The clean state's step 5.8 names these three. P4, P7 (no + second tool for one act).