From 2aa9a96990ac58329e8e72a86fc662856db2c963 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 19:33:29 +0100 Subject: [PATCH] Design 47 H: role names only (hq is public) --- .../H-deliver-the-delivery-system.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) 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 95b0cb90..bdeb730c 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 @@ -61,14 +61,14 @@ per cent of the 527 rows judged (the rest belong to another part's code) (per pa | symptom (live) | count | cause (from the gap tables) | |---|---|---| | wants held or failed on the four machines | 205 held, 66 failed | the catalog half holds no entry for their fingerprints; the node-engines compose nothing new | -| compositions fail on shanks | entries `asked` since 2026-11-18 03:09, unready answers seen from 2026-11-19 11:56 | an entry ask that failed in transport is never asked again; the node-engine's shadow waits on it without bound (the surveyor's reading); other compositions failed on the removed revision trunk.510 and on a call-token refusal | +| compositions fail on the operator's desktop | entries `asked` since 2026-11-18 03:09, unready answers seen from 2026-11-19 11:56 | an entry ask that failed in transport is never asked again; the node-engine's shadow waits on it without bound (the surveyor's reading); other compositions failed on the removed revision trunk.510 and on a call-token refusal | | delivery records open, none ended | 833 open, 0 ended since 2026-11-14 | the gate hears only `take-in.taken`; nothing writes a record's trace, so its difference is never known | | pipelines about to start at the next take-in | about 60 (reasoned from the sweep's rule; no tool reads the runner's waiting starts) | the runner's sweep starts a pipeline for every module whose fingerprint has none (b9c50ef0, 2026-11-16); no design line allows it | | source revision moved twice | both paths on main | A-464 (per merged message) wins live over A-34 (on the take-in): a group's members become separate revisions; a pushed commit reaches the source only through the take-in or the gate's comparison at its next start | | catalog revision removed while pipelines name it | trunk.510 at 22:51 | pins are judged at restart against a key written once; only the take-in pins pipelines | | stale bus state | 753 merges, 6,951 owed, 898 asks, 1,256 pulls keys; 5 pipelines running since midday; 31 stale pin records | buckets of the pre-G model never dropped; no tool reads their contents | | bus load | 98 slow consumers, 117 consumers behind; the watchman 39,037 events behind | mesh-config passes every 5 minutes and polls every minute on main (fixed on the held pull requests); the forge module polls every minute | -| hand-placed programs | every delivery module but the indexer, the image registry and the tool runner (on ace and g14) | G's live start of 2026-11-16 and after; 16 drop-in files under `/run/systemd/system` on the four machines (4 of them `.pre-g` copies), lost at a reboot | +| hand-placed programs | every delivery module but the indexer, the image registry and the tool runner (on the home server and the laptop) | G's live start of 2026-11-16 and after; 16 drop-in files under `/run/systemd/system` on the four machines (4 of them `.pre-g` copies), lost at a reboot | **Every node, every module** (the assigner's assignments at revision 339, unchanged since 2026-11-18 02:08 UTC; the node-engines' haves; read 00:47 to 00:54 CET): @@ -247,8 +247,8 @@ Built 56, built otherwise 8, contradicts 9, missing 3, not judged 7 (of 83). Ass A-478b's order waits on one machine stay (the order waits reshaped to order one machine's apply, not hold wants). - **The assigner reads every have** whole and with history (§520 says it goes); wants are not written from the kept assignment graph revision. Medium each, H1. (The node-engine's read of every node's record stays: it feeds the composer; H-A-60 corrects the earlier reading of §459.) -- **The shanks shadow fault**: the entries client leaves an entry `asked` after a transport failure and never asks - again; about 110 entries on shanks have stood `asked` since 2026-11-18 03:09. Ask again on failure, with a bound +- **The shadow fault on the operator's desktop**: the entries client leaves an entry `asked` after a transport failure and never asks + again; about 110 entries on the operator's desktop have stood `asked` since 2026-11-18 03:09. Ask again on failure, with a bound (small). The surveyor's reading, to be confirmed by `entry-again` on one entry during the clean state. - **The tool runner:** A-490m is ready on mesh-tools #77 (merge); it lacks a test that starts it whole. - **Tests:** the node-engine has 1,719 unit tests against a budget of 500; every change to it shrinks that. @@ -269,7 +269,7 @@ Built 56, built otherwise 11, contradicts 5, missing 11, not judged 9 (of 92). retries twelve watches every 5 seconds; the forge module polls every minute; the build modules re-pull every 5 seconds when idle; mesh-sdk's view catch-up asks again on a timer. The gap table's section 5 has the table of modules, functions and intervals. The fix belongs in mesh-sdk, for every module at once (fix-a-bug-met-twice). -- **`builder_stuck` times out** for a fixed cost, measured in the tool runner's journal on shanks: 1,010 values took +- **`builder_stuck` times out** for a fixed cost, measured in the tool runner's journal on the operator's desktop: 1,010 values took 52.5 seconds and 53 values took 44.5 seconds. Each call starts a tool process that lists every key of `builds` and of every build seat's `steps`, then reads one value per request. The builder keeps its own index of what is building and answers from it. Medium. @@ -373,14 +373,14 @@ like any milestone, but its delivery is by hand, because the running system cann the operator runs each pack one command at a time and says "done"; the lead checks each with the tools before the next: -1. **Freeze.** No merge to any delivery repository but H1's own. The runner on novox is stopped through the service +1. **Freeze.** No merge to any delivery repository but H1's own. The runner on the control-node is stopped through the service seat so no take-in starts a pipeline during the freeze; the assigner stays, so nothing moves. 2. **Merge H1's set to main**, in this order, each reviewed: mesh-contracts #16 and mesh-sdk #200 (held), then mesh-catalog #708 and mesh-delivery #261 (held, mesh-config), mesh-tools #77 (held), and H1's own pull requests (indexer take-in, runner, gate, bridge, assigner, node-engine). mesh-delivery #262 is closed as superseded. The stopped runner starts nothing; the indexer takes the commits in and the gate follows, as the old programs still running during the freeze do. The new programs take every head in once, at the seed (step 5.9). -3. **Build H1's programs from main** with the packs (the g-start phases, one per program), on shanks and novox as +3. **Build H1's programs from main** with the packs (the g-start phases, one per program), on the operator's desktop and the control-node as before, from main's head after step 2 so that main is what runs. 4. **Take the stream snapshot that is the drop's rollback** (design 47 H §765) and test its restore; nothing is dropped yet. The drop-ins are removed and the units the node-engine writes take their place as the wants compose. @@ -455,7 +455,7 @@ at the prepare, one developer per repository on the larger model for the indexer - It does not merge the six held pull requests now; they merge in H1's step 2, and one (#262) is closed. - It does not touch the controller, the vault or the recovery module beyond what the chain needs; the recovery module is not placed and is a later milestone's. -- It does not change the catalog's module set or the build nodes (novox's build agent stays paused). +- It does not change the catalog's module set or the build nodes (the control-node's build agent stays paused). - It leaves what the surveyors could not read as named guesses, each with how to check it, in the gap tables' last sections; the prepare of each milestone checks them.