From d07de2840d4df552d6f3ab97e7eeb7fae4f1f8ab Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 14:47:11 +0100 Subject: [PATCH] Answer A-237c: the token-less inline input stays for the checker until G removes it --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 377173e1..e3dc19f0 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 @@ -1300,3 +1300,7 @@ the principle that settles it, cited as "design 47 G A-n". connection, whatever its size, and its answer names the chunks; the assigner takes it through its ordinary chunked seat call (`CallFile`), as it takes the indexer's `input`. No size bound refuses an input any more. (Live, 2026-11-16: main.952's composition input was 1,000,641 bytes, over the 921,600 one answer carries.) +- **A-237c** (completes A-237b; G-6 §321; principle 7) An ask of `compose-candidate` that names no `call` token (the + checker's, until the checker is removed at G's delivery, G-6 §321) keeps the inline input and its 900 KiB bound; an + ask with a token gets the input in chunks only, with no bound. The assigner reads an inline input only from an engine + that answers no `chunks` (one before A-237b); both forms go with the checker. -- 2.54.0