Answer A-112: a process reads its settings from a declared file

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent 044b913a9e
commit 69771a4d8e
1 changed files with 3 additions and 0 deletions
@@ -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.<verb>`; 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:<key>}`, 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`.