From fd45f0192971f09fc12baa023ed1782a265b731b Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 15:49:03 +0100 Subject: [PATCH] Answer A-424: the operator channel keeps no limit of open asks per asker (the operator, 2026-11-15) --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 558c6db8..26053882 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 @@ -1083,3 +1083,8 @@ the principle that settles it, cited as "design 47 G A-n". 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. +- **A-424** (§394, §450, A-423; the operator, 2026-11-15 about 15:50 CET: "there is no limit for the amount of asks in my + telegram", said many times before; live: the teller held the pipeline's proposal ask behind two week-old asks, since + an asker may have at most three asks open; principles 3 and 7) The operator channel keeps no count of open asks per + asker and holds none back for room: every ask is offered when it is raised. The router's limit, the teller's own and + the ask-again for a held-back ask (§394, §450) go; an ask still lapses at its expiry or ends at its answer.