Answer A-108: the node agent runs the catch-up after the restore

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:51:15 +01:00
parent f29a8f0ebe
commit ccfac82fd1
1 changed files with 4 additions and 0 deletions
@@ -431,3 +431,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `mesh-broker`'s verbs and sends the chunks itself; the builder's process serves `reserved` and `builder_build`; the
  runner's process serves `review`, `rerun`, `accept` and `cancel`, writing `pipelines` by compare-and-set; the chunk
  subjects go to the process that answers.
+- **A-108** (§630, §214, §406, §516; principle 7) The catch-up is the node agent's: after the restore and the `Apply` of
+  the reverted build, it calls the point's recorded `{tool, arguments}` as that module's tool on its own node through
+  the tool runner, as `holder:node-engine` is granted (§406); `restore-kept` carries the snapshot only. §630's "passes
+  its catch-up to restore-kept" reads "runs its catch-up after it".