Answer A-224: one approval gate in mesh-sdk for both gates

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 3f0f6483c8
commit 091551e053
1 changed files with 4 additions and 0 deletions
@@ -173,3 +173,7 @@ the principle that settles it, cited as "design 47 G A-n".
  candidate's catalog half. An unanswered drop is said `call-unanswered` on a five-minute bound key's expiry.
 - **A-223** (corrects A-221; principle 8) A merged pull request's own branch is `head-branch`; `head` stays the head
  commit, as everywhere in the forge messages.
+- **A-224** (§677, A-219; principle 7; code shared between modules is in mesh-sdk) The approval gate is one package,
+  mesh-sdk `go/approval`: the tool runner's gate (node-tools `internal/approval`) moves there and both the tool
+  runner and `go/process`'s seat server use it, each passing the operator channel as an interface (A-219); no second
+  gate is written.