From 8abd0bdb551850623a8071b26881922e570995d7 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:02:09 +0100 Subject: [PATCH] Answer A-71 and A-72: the builder's setting in a file, mesh packages in the build module Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index 9c3018fd..1b55e266 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -275,3 +275,8 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-70** (§572, A-45; the rule that a process answers no call) The builder's tools bundle serves `reserved` and `builder_versions`, following the catalog half's view itself as other bundles follow views; the builder's process serves no call. +- **A-71** (§672, A-55, ADR 0348 §5; principle 7) A process has no settings read, so the builder's + `toolchain-wait-minutes` is placed where config fills a process's settings: a file the manifest declares, its content + `${config:toolchain-wait-minutes}`, read by the builder at its start; never its environment. +- **A-72** (A-56; principle 5) The build modules hold mesh packages as the check does: mesh-build-node's lock problem + and its own install count no `@novox/mesh-*` package as one beyond the SDK.