Answer A-255: the process gate's bound key, header and act

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent ff669cc720
commit 70bfb72c78
1 changed files with 3 additions and 0 deletions
@@ -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.