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 ef676311..53144b58 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 @@ -652,3 +652,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | Proof 1's one line never reached the file: the wallpaper module is a moved module, so its template file is the provisioner's to fill (ADR 0349 ยง4); the node-engine deletes the file's content and hands a plan line to the provisioner, and the provisioner's client renders the files archive on the machine. The provisioner on the control-node runs a build from before the indexer's view rename, asks every minute for a first view the indexer no longer serves (503, no responders), and has made no plan since 2026-11-20 09:41; its own pipeline was the one cancelled in row 126, so no current build of it exists. The node-engines did take feh's new want and its tools bundle within a minute, and the builder did publish the new files archive (its digest moved twice since 2026-11-20) (rows 126, 127 and 128); the provisioner and the runbook. The provisioner goes onto the control-node as a hand pack from main on the operator's word (row 117), and its plan then names the new archive. Owed: a cancelled pipeline's movers get a pipeline again by themselves. | H1 (the pack); H2 (the cancel's movers) | | The four hand packs went onto the control-node between 12:14 and 12:23 (the pipeline runner with its bounded asks, the indexer with its finding kinds, the provisioner from main, the tool runner for seventeen units), every unit active: the provisioner composed every machine from 12:17 without the stale first view; the tool runner's "finding kind not declared" line stopped; the mesh MCP server dropped for a minute at 12:16 and came back by itself; and the big pipeline's validate (row 126's kind) was asked again with the fixed verb at 12:23 and runs under its bound (rows 117, 130 and 133); the runbook. | H1 | | Proof 1 (its second run) is shown: the wallpaper file on the desktop and the build node carries the merged line, read at 12:26. The chain: merged at 11:07:56, taken in at 11:10:47, placed at 11:48:00, passed at 11:49:06, the want written at 11:54:21, the node-engines applied it within a minute, the provisioner's plan named the new files archive at about 12:23 once a current provisioner ran, and the file was written by 12:26. No hand act touched the module's own path; the hand acts were on the delivery system's parts (the assigner on the build node, the cancel of the held pipeline, the provisioner). The time from merge to running was 78 minutes, 37 of them in the queue and 30 waiting on a stale provisioner, so ADR 0282's five minutes is not met (rows 111, 127, 128 and 133); the runbook. | H1 (the proof); H2 (the bound) | +| 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 |