From d02f00bce7ada5da1c1778df29b414a99846a5fb Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 19:42:18 +0100 Subject: [PATCH] Answer A-302: the indexer follows assignments through FollowSeat too; the holder loop goes Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) 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 d035d0eb..afcf4b8b 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 @@ -476,3 +476,6 @@ the principle that settles it, cited as "design 47 G A-n". - **A-301** (§717, A-131; principle 7, one form per seat view) The status view's first-view tool `answers` is mesh-sdk's first-view tool (the one with a callers list, as the assigner's `asks` and `wants` are), its callers the teller in A-131's form; §717's "views.ReadTool" reads as this. +- **A-302** (§717, A-298; principles 1 and 7) The indexer follows the assignments through FollowSeat as well, the + claimant of mesh-module-assigner read from its own catalog (it holds the catalog seat), so buildrun's 5-second + holder loop goes for every part.