Answer A-302: the indexer follows assignments through FollowSeat too; the holder loop goes

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 20:00:56 +01:00
parent 480a857635
commit d02f00bce7
1 changed files with 3 additions and 0 deletions
@@ -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.