Answer A-228: the gate reads everything through interfaces in its own terms

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent e8a2134d94
commit 0dbff50da4
1 changed files with 5 additions and 0 deletions
@@ -189,3 +189,8 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-227** (withdraws A-221 and A-223; §714, §715) As design line §714 says, a merged message gains `base`, the
  watched branch it landed on; `branch` stays the pull request's branch and `head` its head commit, as today;
  `pushed` keeps `branch` for the branch pushed and gains `before`.
+- **A-228** (A-219, A-224; principle 7) Everything the gate reads beyond itself crosses into mesh-sdk `go/approval` as
+  an interface in the gate's own terms, its caller translating from the generated contracts: the catalog's entries
+  (module, fingerprint, serves, manifest), a finding writer (raise and clear by kind and id), the seat holders (a
+  holder function), and the operator channel (ask, record, and claim with the warrant and the act). The gate's own
+  kept form `Kept` moves into `go/approval`, which `operatorchannelclient` re-exports.