From ab39ee3290dc601a019f1a4e2539c2b5ca4baa88 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:42:40 +0100 Subject: [PATCH] Answer A-105: the runner's toolchains state 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 85f65e29..f524e701 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 @@ -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.` 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 ``, value its language, version and digests; a step ask's `toolchain` is read + there.