Answer A-41: no part reads the build modules' toolchains buckets where the builder answers

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:16:58 +01:00
parent feebb8cb20
commit fd04333fa5
1 changed files with 4 additions and 0 deletions
@@ -152,3 +152,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-40** (A-29, A-37; principle 7) The held writer seeds what it holds from its state at `Start`, not when it is
  made, so every module makes it at once, as it makes the plain writer, and no stdio module waits for `Served` in an
  adapter of its own; a `Write` before `Start` is held and written at `Start`.
+- **A-41** (§492, §604, §546; principle 1) A part reads another module's data only by asking it, so the checker and the
+  indexer stop reading the build modules' `toolchains` buckets: they take a toolchain from the builder's own read verb
+  or event where one serves it today. Where none does, the restored read stays for G, built as mesh-delivery 7a3c312a
+  has it, and the lead notes it for the next milestone; no new verb is added in G for it.