Answer A-432: a runtime of its own runs the tool runner's program, which §524's check of the module's parts leaves out

This commit is contained in:
2026-11-16 01:00:35 +01:00
parent 2829a47ea0
commit d9dd5dab67
@@ -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.)