From ae6d3ddecc71b7d0bc5f70cc4d28a895163b8557 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:45:40 +0100 Subject: [PATCH] Answer A-185: the catalog client hands a candidate's revision to a hook Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 83fa5e40..df7c2d2c 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -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.