From 65dcc83bf1f5275a5603a27273d48441047c0b13 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:39:32 +0100 Subject: [PATCH] Answer A-175: the teller and the view follow each other's answers by views families Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 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 2458deb1..f84a1013 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 @@ -659,3 +659,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". members and the modules whose pipeline ended), written on `run-started` and on each of the run's `pipeline-ended`, removed with the candidate, so a restart loses nothing. A member on a branch its registration does not watch takes the trunk's revision view as the base of its take-in; one on a watched branch takes that branch's. +- **A-175** (§512, §431, A-43, A-172; principles 1 and 7) The teller says its `answers` as a plain views family + `views.answers`, and the view says its own `answers` the same way; each follows the other's by mesh-sdk's + `ProcessReader.Follow` (first view through the owner's tool, then its views family). That is the "event" A-172 and + §431 mean; no own follower and no module-event adopt are added.