Design 47 H: lead answer H-A-89 (the record's pipeline families) #761

Merged
mesh-tools merged 1 commits from design/47-H1-answers-23 into main 2026-11-20 02:29:00 +00:00
@@ -367,3 +367,13 @@ Where two preparers disagreed, the chosen one is named.
- **H-A-88 (assigner developer, 03:27)** The seat mesh-wants' `StepRun` gains `asker`, the seat name of the part asking
the step (the runner writes `mesh-pipeline-runner`), a small commit C-W2 by the contracts-indexer-bridge developer;
the assigner names a step's progress with that asker (A11, H-A-41). P8.
- **H-A-89 (gate-and-forge developer, 03:29; the record's pipeline families, §738)** All five as recommended: (1) each
per-mover step result becomes one record outcome, its step the result's step, its outcome the result's own word
(passed, failed, nothing to run, bypass), its why the result's, the entry (module, fingerprint, no node). (2)
`wait-ended` writes over `wait-held`'s `held` under the same outcome key, the outcome the wait's `how` (answered,
ran, superseded). (3) A `pipeline-ended` not passed (failed, refused, cancelled, superseded) ends the record `failed`
naming the pipeline's why. (4) `pipeline-wanted` with outcome `running` ends the record (every tier's movers run on
every present placing machine); `running` events are still written as running-healthy outcomes; `tier-late` ends it
`failed` naming the movers and machines not running. (5) The trace's `from` is the lowest and `to` the highest
assignment graph revision of this pipeline's `wanted` events, each want an entry (module, fingerprint, node) with
outcome `wanted`; a removed want writes nothing. P3, P7.