Answer A-17: the writer names findings-asked with its seat

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
This commit is contained in:
2026-11-11 21:54:44 +01:00
parent 7dc0707008
commit 7c476bfb4a
@@ -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.