From d93dddf5b308ce5783095a5e2704322b1c78c0e3 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 13:59:47 +0100 Subject: [PATCH] Answer A-226c: a run's key reads candidates.run- --- 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 4e82394b..0fcdd926 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 @@ -1288,3 +1288,6 @@ the principle that settles it, cited as "design 47 G A-n". indexer's `runs` state. The seat definition's `candidate` input names the three forms. The assigner builds its key with the client's builder, never by hand. (Live, 2026-11-16: main.948's composition step: "\"main.362\" is not a composition key".) +- **A-226c** (corrects A-226b's run form; A-160; principle 7) For a run's key `run-` the node-engine reads the run's + candidate from the indexer's `candidates` state under the group `run-`, as it reads a check's candidate, with no + heads comparison; the `runs` state holds only a run's members and their ends. -- 2.54.0