diff --git a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md index 41908935..9e380041 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md +++ b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md @@ -655,3 +655,5 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | Proof 2 began: the SDK's one-line change and the tool runner's were merged in one call at 12:26:59 (the seat git's merge verb with two members), the gate moved main's source to one revision for both repositories, and the indexer took both in together at 12:27:18 as one pipeline of 126 movers, the SDK and the tool runner among them (the SDK's release re-pins every importer); the pipeline waits fifth in the queue (rows 127 and 135). The acceptance: the tool runner runs on every machine at the new SDK version with no hand act; the gate, the indexer (`mesh-delivery-indexer`) and the pipeline runner (`mesh-delivery-pipeline`). Owed: a tool that reads one pipeline's movers, with the lighter read per step (row 124's kind). | H1 | | The change of the holder of the seat mesh-wants for row 131 was built, reviewed in two rounds and merged at 12:41 as its own pipeline; the first round found wants written at the start before any revision is kept, and the full-store verdict moved out of the pass, both settled by H-A-261 (no want before a revision is kept; the full-store verdict is the pass's own); the holder of the seat mesh-wants (`mesh-delivery-assigner`). The reviewer's notes stay owed: the bus wrappers' race on one handle, met twice (a handle per goroutine, or a guard in the SDK), and a failed first keeping holding the wants until the next event. Also seen: with the pipeline runner's change live, the waiting pipelines collapsed as designed at 12:38 (three left the queue, their movers moved by the newest), so proof 2's pipeline stands next after the one running (rows 130, 131 and 136). | H1 (the change); H2 (the notes) | | The pipeline ahead of proof 2 (774 steps) made no step the pipeline runner said from 12:42: four contracts modules added to their repository after the registrations' seed of 2026-11-14 were never registered (the seed writes only when no registration is held, and nothing registers a module that enters the module graph later), so their steps waited on a registration nobody had asked, with no bound and no finding (rows 112 and 136); the indexer (`mesh-delivery-indexer`) and the pipeline runner (`mesh-delivery-pipeline`). The build seats were in fact working the other movers while the usage view said none, because it judges a build module by the node-engine's held phase rather than its running asks. The recovery: the four were registered by the register verb, each an Approve on the operator's channel. Settled by H-A-262 (the indexer registers a module the moment it enters a watched trunk's module graph, with no ask, saying registration-changed; the runner raises the finding registration-missing while a mover waits on one), in build in the indexer and the runner. Owed: the usage view judges a build module by its running asks. | H1 (the fix); H2 (the view) | +| The pipeline ahead of proof 2 ended at 13:13:18, its contracts movers still unregistered, and proof 2's pipeline took the slot the same second, placing 182 steps within fifteen seconds; its three contracts movers wait on the same registrations (four Approves open on the operator's channel since 12:59, asked by the indexer at the lead's register calls); a newer merge took 28 movers of the delivery repository out of it at 13:22, while the SDK and the tool runner stay in it (rows 136 and 138); the pipeline runner (`mesh-delivery-pipeline`). | H1 | +| Row 138's fix was built in the indexer and the pipeline runner, reviewed in three rounds and merged at 13:22 as its own pipeline; the rounds found a finding that never cleared, three design points (a pending proposal is skipped; a module the seed left out is not registered by the graph; the branch is the one the siblings hold alike, else the repository's default) and an untested rule, settled by H-A-263, H-A-264, H-A-265 and H-A-266 (row 138); the indexer (`mesh-delivery-indexer`) and the pipeline runner. Its hand packs go onto the control-node next, so the indexer's start pass registers the four modules itself. Owed: a read of the registrations store in one call. | H1 |