From 198d44382a9bb6a3bebb34d684c21b0ce69b2774 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 05:45:49 +0100 Subject: [PATCH] Design 47 H: H-A-121, the clean state's drop tools (mesh-broker.drop, consumer delete, all forms) Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 8 ++++++++ 1 file changed, 8 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 34088e22..1f9b852f 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 @@ -519,3 +519,11 @@ Where two preparers disagreed, the chosen one is named. 0525 §4's deliveries first is corrected to the turns (delivery, check, delivery), citing A-440. H-A-8 and H-A-51's "deliveries first" were wrong: a line existed. ADR 0525 §4 gets a progressive insight in H2 with the builder's lines. P7 (build what the last decided line says). +- **H-A-121 (the clean state's drop tools, 05:46)** The plan's step 5.8 needs tools no module serves (the reader of + 05:43): (1) the bus module serves the seat mesh-broker's verb `drop` (defined in mesh-sdk, class warrant: module, + local-name, warrant, why), dropping one named bucket after a snapshot, and a tool `nats_consumer_delete` (stream, + durable, why) that deletes one durable consumer; both written in the hand-act log. (2) `gate_record_end`, + `assigner_want_drop` and `indexer_pin_drop` take an `all` form (every open record, every held or failed want, every + stale pin) beside their one-item form, each saying what it dropped, counted. (3) The source bucket's old keys are + dropped by `mesh-broker.drop` of that bucket before `gate_source_seed`. Built in H1 on the H1 branches as the clean + state's own tools. P4 (everything that goes wrong can be recovered through tools), P3.