Answer A-106: the runner's steps as built, its write verbs waiting on the operator

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:44:17 +01:00
parent ab39ee3290
commit 362c8074d1
1 changed files with 6 additions and 0 deletions
@@ -418,3 +418,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **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.
+- **A-106** (§25, §416, §535, §647, A-104; principle 7) As built on the runner's recover branch (239a6693, e8b69509,
+  2d9c6591): a kept result counts for an artifact when its package is the artifact's or lies beneath it; the ask's
+  toolchain carries language and version; only the three build seats' asks are bounded by `ask-taken`; the five
+  minutes are a constant; an expired step ends `could not run` and the others run on. The runner's write verbs wait on
+  the operator's answer whether a process may answer calls (then the process writes `pipelines` by compare-and-set
+  itself); the runner gains a whole-module integration test against the bus in G.