Answer A-103: the registration's first branch wins; the follower's helpers built once

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:40:16 +01:00
parent 1c9488c2ae
commit f426b4e5fa
1 changed files with 4 additions and 0 deletions
@@ -404,3 +404,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-102** (§22, §24, A-97; principle 7) A part that puts work on a seat's accepted kind names it in `invokes` as
  `seat:<seat>.<kind>` (the runner: `seat:mesh-builds.step` and each build seat's `check.step`), and the grants part
  composes the publish of that accept subject from it, as it composes a verb's call.
+- **A-103** (§532, §614; principle 7, shared code in the follower) When two watched branches list one module, the
+  module's own registration decides: its first branch is the one read. The `Entry` and `Ready` helpers over the branch
+  follower, the `<module>_entry_again` tool, the `entry-not-found` finding and the entries rows of
+  `<module>_first_views` are built once, in `meshcatalogclient` and mesh-sdk's views, and every reader uses them.