From 77379f62ce8b094be274aa0969da6809187c15c1 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 11:47:17 +0100 Subject: [PATCH] Answer A-280: a bundle's findings follow its membership's finding-events stream Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 64e461c9..c231bcef 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 @@ -378,3 +378,8 @@ the principle that settles it, cited as "design 47 G A-n". event and keeps the base on the pull request's `MergePull` in its state `merges`, the entry the Approve makes; the verb `groups` answers a group with no record yet from `merges`, and the take-in copies the base onto the record's `RecordGroup.Pulls` when it opens the record. No new state; the take-in's branch never stands in for it. +- **A-280** (A-274, ยง529; principles 1 and 7) A tool bundle's finding writer (`views.NewStdioHeldWriter`) changes + nothing: the tool runner already publishes an emitted event on the subject of the first stream of the module's + membership that carries it (node-tools `bus.eventSubject`). The grants part lists a module's required + `finding-events` stream in its membership with that subject and the finding events, so a bundle's findings land + under its binding as a process's do; with no such stream they stay on EVENTS.