From 7c476bfb4a2d63974d0d418e6e163fb94a11129c Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 21:43:47 +0100 Subject: [PATCH] Answer A-17: the writer names findings-asked with its seat Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index 2088c0b5..ade67fd7 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -65,3 +65,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". one mesh-sdk constructor, `views.NewStdioWriter`, generic as the writer is,, which fills `Publish` from the module's own event publish and `Listen` from its subscription; no module writes that adapter. The tool runner's own finding writer (mesh-tools' first views) hands in `Publish` and `Listen` from its bus connection, in its one place. +- **A-17** (ยง461, A-16; principle 7) `findings-asked` is always the seat `mesh-conditions`' event, so the writer names it + with that seat, `mesh-conditions.findings-asked`, as a constant of mesh-sdk, in Go and TypeScript alike; no module + supplies it.