From 04955c3112fefb5515ad6df686edfcc74e504312 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:18:57 +0100 Subject: [PATCH] Answer A-237: a run's input is any size, served in chunks Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 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 9e1119b6..dafe77d8 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 @@ -224,3 +224,7 @@ the principle that settles it, cited as "design 47 G A-n". branch>`), `before` read from it and its start read comparing with it; `pushed` carries the same take-in inputs as `merged`. For §715 the mesh-delivery seat's `groups` member gains `base` in the contract, which the gate fills and the bridge reads. +- **A-237** (§712, §354, ADR 0666 §16, A-139; principle 7) A run's input is any size: the indexer keeps it in its state + `inputs` with the state's `-objects` store holding a large value (mesh-sdk's `stateobjects`), and serves it through + its `input` verb answered in chunks (`buscalls.SeatChunks`, a verb marked `chunks`); `RunInputBound` goes, and the + holder takes the input by that verb.