Design 47 H2: H-A-405, a kept chunked call in mesh-sdk; the compose-candidate ask id

This commit is contained in:
2026-11-22 00:52:44 +01:00
parent 3900d17bb1
commit 15ef740ef5
@@ -286,3 +286,11 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
(the holder's one store for asks by id, P3; ADR 0664 §4's kept drop): a pull within the bound ends the step
could-not-run naming the drop (H-A-401); past the bound the runner's step has ended already and the key is gone. A
taken ask that runs is cancelled in the run that holds it, as built. P3, ADR 0664 §4.
- **H-A-405 (a kept chunked call lives in mesh-sdk; a compose-candidate ask's id is the step ask's with the node,
00:54)** §775, A1. (1) A kept, ask-carrying chunked call is mesh-sdk's (code shared between modules belongs in the SDK;
one form for every kept call, P9): process gains CallChunksKept and CallFileKept, which pace with busretry.DoPaced,
carry the one ask id in stdio.AskHeader on every chunk, and stop at the caller's bound as the plain kept call does; a
mesh-sdk subtask S14, built now by a mesh-sdk developer; the assigner calls it. No pacing of the plain CallFile in the
assigner and no ask without an id. (2) The compose-candidate ask's id is `<step ask>.<node>`: the pipeline step's ask id
with the node asked, so one id per node per step, unique in the engine's mesh-wide taken bucket keyed
node-engine.<ask>; a repeat to the same node carries the same id and joins the run (H-A-364 (b)). P3, P9, ADR 0668 §2.