Answer A-185: the catalog client hands a candidate's revision to a hook

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 8834af8bd0
commit ae6d3ddecc
1 changed files with 3 additions and 0 deletions
@@ -22,3 +22,6 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-184** (clarifies A-170; §543; principle 3) Until main's subject goes, it also takes the checker's `check` and
  `recheck` asks, so no ask that runs today is refused by G; a queue is only `delivery`, `check` or `recheck`, and
  steprun's `AskKinds` lists no `step` queue.
+- **A-185** (A-180; principle 7) The catalog client (`meshcatalogclient`'s catalog follower), which already hears every
+  `catalog-revision`, hands a candidate's revision it does not keep to a hook its caller sets; the runner sets it to
+  place a run's pipelines. mesh-sdk's event hub keeps its one handler per pattern.