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 ef79879a..a2214380 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 @@ -905,3 +905,9 @@ The lead's one-line answers to the questions H2's develop and review raise (impl with both gets both), so the pass makes no orphan from now on and removes nothing a live program reads; the tool runner removes nothing at start. (1) and (2) stand; "current" is pulls waiting and a delivery within the day. A twin is the pair with the `_tools` suffix and no other. P3. +- **H-A-472 (second addendum, 14:35)** The composer's reading, from the live bus: `_` is composed for a + module with an account of its own (an own broker secret) and a process resource with no `bus` of its own; no other + field tells it, and this misses no live reader. `__tools` stays composed for every consuming module as + today, since no field the runner and the composer share says which modules the runner reads for; the stray ones are + named by durable-orphaned and removed with the tool. A field that says who reads a module's events (its own program, + the tool runner, or both) is the thorough shape, noted for H2b. P3, rules-are-weighed (said).