Answer A-206: the runner's release verb, its wait finding and clock

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent d60302b2bd
commit 18ecf1c47f
1 changed files with 5 additions and 0 deletions
@@ -104,3 +104,8 @@ the principle that settles it, cited as "design 47 G A-n".
  `revision`: for a run, with `group` `run-<id>` (the candidate's newest); for a source revision, with `branch` and a
  new optional argument `source`, answering the branch's revision taken in from that source revision. It answers the
  permissions the composed memberships gain and lose with the candidate's entries in place of the branch's newest.
+- **A-206** (A-195, §65, §534, A-181; principles 3, 4 and 8) The runner's held pipelines are released by hand through
+  a seat verb `release` of `mesh-pipeline-runner` (class act, its hand act written first), beside `start` and
+  `ask-again`, its tool `runner_release`; the bound's expiry writes the finding `pipeline-waits` (scope `module`, id
+  `<branch>.<id>.<module>`); the wait's `on` gains the value `runner version`; its `clock-from` is the `build.ended`
+  of the awaited fingerprint, heard as A-181 says.