From 69771a4d8efa74d0a92ded18e3f90a5544e18789 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 00:20:20 +0100 Subject: [PATCH] Answer A-112: a process reads its settings from a declared file Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 3 +++ 1 file changed, 3 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 2db785ac..90359c59 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 @@ -448,3 +448,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". `ask-again`; `cancel` drops the asks' bounds and leaves what the build seats already took; the hand act's verb is `mesh-pipeline-runner.`; a review ends every running pipeline at that commit and fingerprint waiting on one. A review given after a pipeline ended passed is refused, as built. +- **A-112** (ยง633, A-71; principle 7, one way per kind of part) A process reads its settings as the builder does + (A-71): a file its manifest declares, its content `${config:}`, read at its start; so the node-engine reads + `recovery-wait-minutes` from such a file, default 90 when it is missing. A bundle keeps `stdio.Config`.