From 88c44c095e8eda0516cce6695ccab716db5039e6 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:21:00 +0100 Subject: [PATCH] Answer A-238: a run ask may name no head Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 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 dafe77d8..908c796c 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 @@ -228,3 +228,6 @@ the principle that settles it, cited as "design 47 G A-n". `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. +- **A-238** (ยง712; principle 7) A run ask may name no head: `RunJob.check` takes an empty `Heads` when the program + is named, and the holder lays an empty `MESH_RUN_HEADS`; the validation's program is built from the indexer's + entry alone.