Answer A-225 and A-226; code-span a module name in A-224

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md

@@ -174,6 +174,15 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-223** (corrects A-221; principle 8) A merged pull request's own branch is `head-branch`; `head` stays the head
   commit, as everywhere in the forge messages.
 - **A-224** (§677, A-219; principle 7; code shared between modules is in mesh-sdk) The approval gate is one package,
-  mesh-sdk `go/approval`: the tool runner's gate (node-tools `internal/approval`) moves there and both the tool
+  mesh-sdk `go/approval`: the tool runner's gate (`node-tools` `internal/approval`) moves there and both the tool
   runner and `go/process`'s seat server use it, each passing the operator channel as an interface (A-219); no second
   gate is written.
+- **A-225** (A-173, §532; principles 2 and 7) The view keeps each repository's reach in its own state on the bus, so a
+  restart does not lose it; its history is the source revisions heard since its start, re-asked through `source` on
+  each `source-moved`, laid over the reach it kept.
+- **A-226** (A-167, §354, §64, §63, A-174; principles 2 and 7) The composition step asks each node's
+  `compose-candidate` with the key the step's pipeline names: a run's candidate `run-<id>`, or for a branch pipeline
+  the branch's revision `<branch>.<revision>`, which the node-engine reads as it reads a candidate. It runs
+  `mesh-compose` once per node-engine fingerprint among the machines (the change's build where the change alters the
+  node-engine, §63), the program read from that fingerprint's catalog entry through `entry`, each run's request
+  joining the inputs of the machines on that fingerprint.