diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 67e9dde6..3d9d74f8 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -2344,3 +2344,12 @@ Where two preparers disagreed, the chosen one is named. mesh-delivery developer (the runner's placing and the delivery SDK's step run) after its Left list, in H2's one review; it is not a small fix. Until then a could-not-run step is rerun by hand (runner_rerun). P-NATS-native, P-failure-loud, ADR 0552. +- **H-A-376 (the runner's list answers a short form, 23:53)** The operator asked where to follow the pipelines; the + runner's list of main answers 2.3 MB, above what the bus carries, and show of one pipeline 127 KB, so the state can + only be read narrowed by module, mover and limit, and stands has no description. One question, one tool: list + answers by default a short row per pipeline (key, call, started, ended, outcome, the movers' count, the first failed + or could-not-run step with its module and why), the newest 20, and the whole pipelines only with `full: true` and a + limit; show answers the steps of one mover when given, else the pipeline's rows per mover (module, outcome, the + failed step) and never every step of every mover; stands, kept and why-carried get the description their seat + contract names. Built by H2's mesh-delivery developer after its Left list. tools-are-how-a-module-is-spoken-to, + one-question-one-tool, P3.