Answer A-237: a run's input is any size, served in chunks

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent eba38e5ed9
commit 04955c3112
1 changed files with 4 additions and 0 deletions
@@ -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.