From a0147f94af015e318ba7f28e49df907598eeb6cd Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 21:35:48 +0100 Subject: [PATCH 1/2] Answer A-304: the checker puts a phase's asks at once and holds no step Try 4 and 5 ran their steps one at a time because the checker waited on each ask before putting the next. Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 8608d572..66c2a5f1 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 @@ -485,3 +485,8 @@ the principle that settles it, cited as "design 47 G A-n". matches what the watchman writes), the view takes it at run time from the holder FollowSeat follows, through one accessor of the SDK's process reader; no code names the assigner's module. *Corrected 2026-11-12: it first named the reach history's bucket names as real buckets too, for kept entries' sake; the view's kept reach holds no bucket name.* +- **A-304** (ADR 0525 ยง4, A-284, A-285; principles 7 and 1; the operator's yes, 2026-11-12) The checker holds no + step: within each of its two phases (every module that is not TypeScript, then the TypeScript modules after + `groupPackages`) it puts every ask of the phase on the check stream at once and then waits for all of them, so the + build nodes pull them at their own capacity; a declined ask is put again as today, and the phase's verdict is judged + in the same order as before, whatever order the asks end in. From dce214b7f566b4971c9d0c8b7c8b2d37f8a15d70 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 21:47:56 +0100 Subject: [PATCH 2/2] Answer A-305: the pipeline runner's health is its unit, like its siblings' Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 ++ 1 file changed, 2 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 66c2a5f1..6e543ed9 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 @@ -490,3 +490,5 @@ the principle that settles it, cited as "design 47 G A-n". `groupPackages`) it puts every ask of the phase on the check stream at once and then waits for all of them, so the build nodes pull them at their own capacity; a declined ask is put again as today, and the phase's verdict is judged in the same order as before, whatever order the asks end in. +- **A-305** (ADR 0227 rule 8, ADR 0240 rule 2; principle 7) The pipeline runner's process declares the health `unit`, + as every other process of mesh-delivery does; `runner_health` stays a tool and judges nothing for the node-engine.