From 201e998418bff9fe5705e3540ff57e4d033ef14f Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 21:59:52 +0100 Subject: [PATCH] Answer A-27: the tool runner's first views are adopted by a process reader 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 979245a6..e5aa88c6 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 @@ -103,3 +103,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-26** (§687, §689, A-22; principle 7) A part raises no follower's finding itself: every follower is adopted through its reader (`Adopt`), and the reader raises and clears the follower's four findings through the module's writer, so the pipeline runner, the indexer and the assigner build none of their own. +- **A-27** (A-26, A-16; principle 7) The tool runner's first views follow A-26 too: `firstview` builds a + `views.ProcessReader` over the runner's bus connection and adopts its followers, so the reader raises their findings; + the runner's `bus.Conn` gains one accessor for its JetStream, its one place (A-16).