From 3679bec24aa1c6e3a7d2b0ac3b56a1a94028265a Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 02:26:40 +0100 Subject: [PATCH] Design 47 H2: H-A-454 addendum, the builder's process keeps the module's account --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 9050e849..766a65cf 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -693,3 +693,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl its own stream (the counts per holder and class, the oldest and newest, a capped list), and the tools program's builder_publish_queue calls it, as the runner's tools call its seat's verbs. builder_publish_drop and _first stay as H-A-448 has them (reasks the builder performs). The validator gains no exception. P-NATS-native, P3, ADR 0619 §1. +- **H-A-454 (addendum, 03:05)** The builder's process keeps no `bus` of its own: it runs on the module's account as + today, and `publishes` is a module stream of the old streams section with the work-queue retention (ADR 0436 §6), + which the process consumes on that account; a process's `bus.queues` names a queue only for a process with an account + of its own, which the builder's is not. A validator refusal of that form, if one comes, is the next question. P3.