From fbff9aa30659dd5ed265ab47b4df2260de4ef82d Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 05:48:44 +0100 Subject: [PATCH] Design 47 H: H-A-121 corrected (module tools, not a seat verb); H-A-122 the mail reader's callers list goes Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- .../01-to-be/47-milestones/H-lead-answers.md | 21 ++++++++++++------- 1 file changed, 13 insertions(+), 8 deletions(-) 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 1f9b852f..867f07ac 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,11 +519,16 @@ 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. +- **H-A-121 (the clean state's drop tools, 05:46; corrected 05:52)** The plan's step 5.8 needs tools no module serves + (the reader of 05:43): (1) the bus module gains two tools beside the seat mesh-broker's verbs: `nats_drop_bucket` + (bucket, why: drops one named bucket after a snapshot) and `nats_consumer_delete` (stream, durable, why: deletes one + durable consumer); both written in the hand-act log. They are the operator's hand tools for one module's own kept + data, not a need another module fills: a module tool, not a seat verb (P9; the seat's definition stays as reviewed). + (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 go by `nats_drop_bucket` 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. +- **H-A-122 (the mail reader's callers list, 05:52)** Goes, like every other holder's (H-A-41, H-A-66; ADR 0682: every + account may call every verb). The mesh has one user and is assumed not compromised (the operator, 2026-11-11); who + inside the mesh may read mail through a verb is who-may, a design detail, not public exposure: nothing here puts mail + outside the mesh. ADR 0459 §2's protection of mail data stays in what the verbs answer, not in who may call them. P1.