diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
index 8f94ea8e..2853dcf1 100644
--- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
+++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
@@ -347,3 +347,9 @@ the principle that settles it, cited as "design 47 G A-n".
   the runner's own record of the calls its gate holds; it keeps no `call.` keys of its own for it.
 - **A-272** (§677, ADR 0596; principle 1) The `GateChannel` over `process.Conn` asks and reads an ask only through
   mesh-sdk's `operatorchannelclient` on the seat `operator-channel`, never through the router's bucket.
+- **A-273** (corrects A-272; §700, A-74, A-89; principles 1 and 7) The `GateChannel` over `process.Conn` is §700's:
+  `operatorchannelclient.Client` given, as its `Record`, a get of the key under `<module>.` in the seat
+  `operator-channel`'s state `asks` (the bucket formed from the seat's holder on the seat list and `StateAsks`, A-74)
+  on the process's own connection; the verb `asks` stays as it answers. The ask is published by a new `go/process`
+  method that publishes on a seat's accept subject (`mesh.seat.<seat>.accept.<queue>.<caller>`), on the a3g line,
+  as `Emit` publishes an event.