Merge pull request 'Design 47 G: lead answer A-304, the checker puts a phase's asks at once' (#591) from design/47-G-lead-answers-19 into main

This commit was merged in pull request #591.
This commit is contained in:
2026-11-12 20:51:13 +00:00
@@ -485,3 +485,10 @@ 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 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 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.* 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.
- **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.