From 3c40a6e6c8151799d3970a45102bc125dc15333d Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 11:47:35 +0100 Subject: [PATCH] A-280: the code name in a code span Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 c231bcef..c3ef61f9 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 @@ -380,6 +380,6 @@ the principle that settles it, cited as "design 47 G A-n". `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 + 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.