Answer A-105: the runner's toolchains state

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:42:40 +01:00
parent 9efa510ad5
commit ab39ee3290
1 changed files with 3 additions and 0 deletions
@@ -415,3 +415,6 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `toolchain` is the runner's `toolchain.<language>` kept as heard from `toolchain-agreed`. An unanswered ask is read
  from the build seat holder's `ask-taken` as §647 says (not the seat list), its five minutes a key with its own time to
  live in a state `bounds` of the runner.
+- **A-105** (A-104; principle 7) The runner keeps what it hears of `toolchain-agreed` in a state of its own,
+  `toolchains` (history 1), key `<language>`, value its language, version and digests; a step ask's `toolchain` is read
+  there.