Answer A-244: wait held is a header; the held answer a field of its own

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 3b309fa61e
commit 2904b60c1e
1 changed files with 5 additions and 0 deletions
@@ -250,3 +250,8 @@ the principle that settles it, cited as "design 47 G A-n".
  `mesh-wants`' `input` too): any size, kept with an `-objects` store, answered in chunks. The composition run names
  no head (A-238); its program is the node-engine fingerprint's entry (repository, commit, directory) with the
  composer's package.
+- **A-244** (§677, A-186, A-219; principles 7 and 8) `wait: held` travels as a bus header on the request, never as an
+  argument, so no verb's input and no act's digest changes; the holder's held answer is a reply field `held`
+  {asked, call} beside result, error and node. `process.Conn`'s seat call sends the header on every seat call and
+  waits for `gated-ended` only when the reply says `held`. A process holder applies the seat definition's
+  `needs-approval` alone (the definition `AnswerSeat` is given); it reads no catalog entry.