Design 47 H: lead answer H-A-75 (pipeline-wanted's outcome and body; the node's own want unchanged) #748

Merged
mesh-tools merged 1 commits from design/47-H1-answers-10 into main 2026-11-20 02:03:32 +00:00
@@ -302,3 +302,8 @@ Where two preparers disagreed, the chosen one is named.
field, now absent from the contracts; the builder has none, so nothing of the builder changes in H1. G §672's
toolchain wait (the state `waits`, its events, tools and setting) is a build's wait for its toolchain, not a want's
hold on another delivery, and stays: §764 names no builder item, and the builder's lines are H2's. P7; ADR 0682 §9.
- **H-A-75 (contracts-indexer-bridge developer, 03:02; the seat mesh-wants)** (1) `pipeline-wanted.<branch>.<source>` is
said once per pipeline, at its end: `outcome` is `running` when every tier's movers run (the node-engine seat's word,
P8) and `tier-late` when a tier passed its bound, the body `{v, pipeline, branch, source, outcome}` and, for
`tier-late`, the movers and machines not running. (2) H-A-37's drop of `composed` is the module want's alone; the
node's own want `want.<node>.node` `{composed, words, self}` is unchanged, and `rank` is absent from it. P7.