From 98e8bc395b88e99b72ffbf7f888aa4a33d9c9d01 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:03:19 +0100 Subject: [PATCH] A-397: the operator's decision time read from the clock --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 e3701472..1aff7b0b 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 @@ -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 `_`, 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