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 2853dcf1..5b7eb836 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
@@ -353,3 +353,9 @@ the principle that settles it, cited as "design 47 G A-n".
   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.
+- **A-274** (§529, A-13, A-30, §584, §627; principles 1 and 7) The held finding writer takes its subjects from the
+  part's own binding: when the process was handed a binding of the local name `finding-events` (an `events`
+  template its manifest requires), it publishes under that binding's subjects
+  (`mesh.bus.<module>.finding-events.<event>.<node>`); with no such binding it publishes on the old stream
+  (`mesh.stream.<module>.event.<event>.<node>`). The module passes no subjects (A-13 holds) and the SDK keeps no
+  foundation list.