A-397: the operator's decision time read from the clock

This commit is contained in:
2026-11-14 18:03:19 +01:00
parent ed95207361
commit 98e8bc395b
@@ -896,7 +896,7 @@ the principle that settles it, cited as "design 47 G A-n".
- **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
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 `<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