From c94a65f2d8e3fe52533021e89a928af44001feb8 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 11:00:39 +0100 Subject: [PATCH] Answer A-274: the finding writer takes its subjects from the part's own binding Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) 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..accept..`), 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..finding-events..`); with no such binding it publishes on the old stream + (`mesh.stream..event..`). The module passes no subjects (A-13 holds) and the SDK keeps no + foundation list.