Answer A-397: every process that hears events has a durable consumer of its own, named constantly; a shared one split the first registrations between the assigner's program and its tool runner
This commit is contained in:
@@ -893,3 +893,13 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
since no build module's manifest invokes them; principles 7 and 4) Every module is composed as invoking the tool runner's
|
||||
own reads (the seat list's verb, the catalog half's revision and registrations, the delivery seat's source), so each
|
||||
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:10: "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 `<node>_<module>`,
|
||||
its tool runner `<node>_<module>_tools`, any other process its manifest names `<node>_<module>_<process>` (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.
|
||||
|
||||
Reference in New Issue
Block a user