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 a3eb67e6..a234eb8a 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 @@ -284,3 +284,12 @@ Where two preparers disagreed, the chosen one is named. asker judgement in `mesh-delivery-sdk/steprun` (H-A-41) is the contracts-indexer-bridge developer's subtask, since that package is mesh-delivery's shared code and it already writes there; the three build modules' wiring stays mesh-catalog's BUILD-1. The lead's order of work. +- **H-A-72 (contracts-indexer-bridge developer, 02:53; the runner's and mesh-wants' seats)** (1) The pipeline value: + `group` goes; `module`, `commit`, `fingerprint`, `repository`, `version`, `widens`, `tests` and `over-budget` move into + each mover; `run`, `published`, `unlogged` and `end-count` stay on the pipeline (P7). (2) The runner's state `queue`: + `queue.next` and one key `waiting.` with value `{pipeline}`, so the lowest sequence is read by key + order (P1). (3) `wait-held` and `wait-ended` move to the one subject form `.`, the body naming the + module for a step's wait (P8). (4) The step events and `run-started` keep `..`, the + commit-or-group token becoming `` (P8). (5) `pipeline-ended` carries per mover its step results as a list of + step results, each naming its module (H-A-35, P10). (6) The tier end is a second event of the seat mesh-wants, + `pipeline-wanted..` with `outcome`; `wanted` stays per node and module (P8); H-A-56 reads so.