From d9dd5dab67a2cba74d58e10cd160340e53d0ec2d Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 01:00:35 +0100 Subject: [PATCH] =?UTF-8?q?Answer=20A-432:=20a=20runtime=20of=20its=20own?= =?UTF-8?q?=20runs=20the=20tool=20runner's=20program,=20which=20=C2=A7524'?= =?UTF-8?q?s=20check=20of=20the=20module's=20parts=20leaves=20out?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 e6ae70d3..177a8b2e 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 @@ -1164,3 +1164,8 @@ the principle that settles it, cited as "design 47 G A-n". the same `branch`, `source` and `entries`, so a reader keyed by branch and source revision (the runner, the gate) acts once; a taken event that took nothing in (a group's end, one said before G) carries none, and the runner writes it in its journal and lets it go (§493). +- **A-432** (§524, ADR 0259 §8; principle 7) A module of its own account is run by a runtime of its own, a process + whose program is the tool runner's build, not the module's: the check of §524 leaves that process out, and the tool + runner's own want checks its program. Every other archive, process and container of the module's composition is + checked against its want's `parts` as §524 says. (novox, 2026-11-16 01:00 CET: the new indexer was held + "parts-differ: fetched and not in the want's parts" for the tool runner's program.)