diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 283be323..23486625 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -895,14 +895,14 @@ the principle that settles it, cited as "design 47 G A-n". account the runner serves a module on may ask them. - **A-397** (live, ace 2026-11-14: the assigner's program and its tool runner both bound the durable consumer `ace_mesh-delivery-assigner` on `SEAT_mesh-catalog_registration-changed`; the runner pulled all 178 events of the first - registrations and the program, which acts on them, heard none and said nothing; the operator decided, 2026-11-14 about - 18:00: "a constant name for each separate process"; principles 1 and 7) Every process of a module that hears events - hears them on a durable consumer of its own, named constantly across restarts: the module's program `_`, - its tool runner `__tools`, any other process its manifest names `__` (A-340). A - durable name holds no dot (design 19 *The consumer*). Only a work queue's consumer is shared, by the processes its - `bus.queues` names. The grants part composes and makes each of them, with the hear of exactly that process's events; a - process that binds a consumer composed for another process is refused at its start, said in its log. This amends - design 19's *one durable consumer per module*, written when a module was one process. + registrations and the program, which acts on them, heard none and said nothing; principles 1 and 7) A durable name is + shared only where the work is meant to be shared: a work queue, each item to one taker, as NATS shares one durable among + its pullers. Every other reader needs every message, so each process of a module that hears events has a durable consumer + of its own, named constantly across restarts: the module's program `_`, its tool runner + `__tools`, any other process its manifest names `__` (A-340). A durable name holds no + dot (design 19 *The consumer*). The grants part composes and makes each, with the hear of exactly that process's events. + This is a builder's judgement no design line overrode (the operator, 2026-11-14: "the developer should use his brains"); + design 19's *one durable consumer per module* was written when a module was one process. - **A-398** (live, shanks 2026-11-14 18:13: the G builder was refused `KV_mesh-build-go_steps` and the image and node steps, since its reads `seat:node-build-{go,image,node}.steps` resolved to no holder: no assignments holds the build seats; the operator decided, 2026-11-14 about 18:16: "yes, do it", after their word of 16:45 that who holds a seat follows from the