From 5f761c16cd19bf5ba2f384852e5425f852780446 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:04:05 +0100 Subject: [PATCH] Answer A-213: the indexer asks the validation run; the rest to design lines 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 ae31fe8e..063f2ebb 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 @@ -136,3 +136,7 @@ the principle that settles it, cited as "design 47 G A-n". - **A-212** (§47, §432, A-208; principle 8) An edge of kind 2 comes from a `needs` reference to another module's artifact: that is what an artifact "fetches by reference at its start", so the referenced artifact is published before the referring one delivers. Kind 5 goes to a design line (which acting steps give it, and between what). +- **A-213** (corrects A-86; §16, §354, §206) The indexer does ask node-build-go's `run` for its validation of a + revision before its take-in, as §16 says; A-86 holds only for `KeepInput`, which the indexer's `input` verb calls + for a run on request's asker. The run's input and job, what holds the pending revision meanwhile, and how a non-trunk + branch's pending revision and groups are made go to design lines.