From f0b9c73a9f2efa3cffc6a287ea22166672e1aa4f Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 03:52:41 +0100 Subject: [PATCH] Answer A-423: one reader per durable through the hub; a consumed kept event with no route is said --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) 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 e13b2c03..558c6db8 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 @@ -1076,3 +1076,10 @@ the principle that settles it, cited as "design 47 G A-n". a stream it cannot bind is said in its log and its start goes on. The replay of what waited is heard as any event; a part whose handler cannot take its backlog is a finding of the change, read before its delivery. (Thorough fix, said: the indexer's own call, b0242f68, is the quick fix placed meanwhile.) +- **A-423** (A-397, A-422; read from the code 2026-11-15: the assigner reads machine-away and machine-back, and the forge + bridge branch-moved, with readers of their own on the durable the hub now binds too, so each message would reach one + of the two; and the checker, the forge bridge, the view and distribution consume registration-changed in their + manifests with no route, so its durable fills unread; principles 1, 3 and 7) One reader per durable: the hub is the + only reader of a part's kept streams, and a part that read one itself hands its handler to the hub, which gives each + event to every handler it has for it. A kept event a part's manifest consumes and no route takes is said at its start, + naming the event, as a fault of the part to be fixed in its manifest or its code.