Answer A-219: the gate takes the operator channel as an interface; only Act moves

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent beac2c0170
commit 1fa531268b
1 changed files with 5 additions and 0 deletions
@@ -156,3 +156,8 @@ the principle that settles it, cited as "design 47 G A-n".
  seat's `entry`, and `FormChanges` compares it with the want's entry.
 - **A-218** (A-206, §696; principle 3) `pipeline-waits` is cleared when the node-engine seat's `running` says the
  awaited runner fingerprint healthy; A-206's `runner version` holds over §696's wording.
+- **A-219** (refines A-198; §677; principle 7, one form for each thing) Only `Act` and `ActDigest` move into mesh-sdk's
+  `go/operatorask`; the ask's types stay the generated seat contract's. The gate in `go/process` takes the operator
+  channel's calls (ask, read the warrant, record) as an interface its caller passes, which `operatorchannelclient`
+  implements over the generated types, so no form is copied and no import cycle arises. The seat client's
+  `wait: held` lives with `process.Conn`'s call, as there is no `go/seats`.