From 70bfb72c78cc6097e2e9a3da5fa4449837e3ec24 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 09:31:51 +0100 Subject: [PATCH] Answer A-255: the process gate's bound key, header and act Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index f9cc84c2..059f0401 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -292,3 +292,6 @@ the principle that settles it, cited as "design 47 G A-n". `output-object`, the name of an object the build seat keeps, read through the seat's verb `output` answered in chunks. Every build seat (`node-build-go`, `node-build-image`, `node-build-node`) says it the same way, from the shared step runner; no asker reads the seat's step state. +- **A-255** (ยง677, A-77, A-244; principles 1, 7 and 8) The header is `x-wait: held`. A process holder's + `gate-unanswered` is a bound key with its time to live in the `approvals` state, as the tool runner's `bound` is, + never a clock wait. A process holder's act names no node, so two instances of the holder raise one ask.