Answer A-237c: the token-less inline input stays for the checker until G removes it

This commit is contained in:
2026-11-16 14:47:11 +01:00
parent 2ab0507440
commit d07de2840d
@@ -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.