Answer A-305: the pipeline runner's health is its unit, like its siblings'

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 21:47:56 +01:00
parent a0147f94af
commit dce214b7f5
1 changed files with 2 additions and 0 deletions
@@ -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.