Design 47 H: section 10, finding 197

This commit is contained in:
2026-11-21 21:27:03 +01:00
parent 9b9f528e35
commit 5367dc409f
@@ -713,3 +713,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| The restart of row 193 ended the catalog repository's pipeline at 21:15:30 through the pipeline runner's start pass (row 159's rule that ends an empty pipeline, at work): it ended failed on the Node build module's integration tests, whose setup took forty seconds against a thirty-second bound while three nodes' checks ran, and on the recovery module's whole test; the zfs and forge test fixes passed in it, so their kinds are closed, while the laptop's Go build module stays at its earlier release, since a failed pipeline writes no wants; the next pipeline was placed at 21:15:42 (rows 159, 165 and 193); the pipeline runner (`mesh-delivery-pipeline`), the Node build module and the recovery module. Owed, by H-A-327, of H-A-294's kind: a setup bound read from the step's own bound; a whole-module test that needs the bus's time under load says NOT RUN rather than failing; both fixed in their modules before the next release that carries them. | H1's tail (recorded); H2 (the two tests) |
| H-A-326's read (row 193) met the fact that the pipeline runner's record knows only the publishes it heard, and a package published before a pipeline existed is in no record of it (the two movers' packages had been published by an earlier pipeline at 20:00); the builder owns publishes, so H-A-328 gives the seat mesh-builds a read verb `published` (module, artifact and fingerprint; answering published, version, digest and when), served by the builder from its reservations and the registries' record, which the runner asks once when it writes a mover's wait on a package, the publish event staying the second path. The seat mesh-builds is defined in the delivery repository's own contracts module (not in the contracts repository, as the lead's map had it; H-A-328 is corrected so), so the runner's open branch stays one branch in one repository, holding the seat's definition, the builder's serving and the runner's asking, and the fifth merge waiting on the operator (row 190) keeps one head, new after its review (rows 190, 193 and 194); the pipeline runner (`mesh-delivery-pipeline`) and the builder. | H1's tail (the runner and the builder) |
| The packet filter's group was complete at 21:23, an hour after the operator's decision (rows 180 to 195): the networking repository's seat definition, made whole (the six verbs, the event, the state per machine, a kept allowance naming its outward link, rules listing what is loaded but not kept); the catalog repository's holder (27 tests, type-checked against the generated packages, the catalog's 33 checks green, the manifest validator accepting its manifest); the contracts repository's seat of the node-engine (the read verb `converged` with the node's state and links, the composition answer's withheld parts); and the node-engine (the compose asking allowed within its bound, the filter kept as it runs when unanswered, the render with timed sets and the default excluding outward links, the event heard, `converged` served from the render's own sources); the one review of the four heads began at 21:24. One fact for the pipeline's check: the manifest validator, run against the trunk's seat files, refuses the node-engine's manifest in both cases for a cause that predates the change (two registry seats' versions verbs absent from those files), which the live seat list is believed to carry; the pipeline's own validate decides (rows 186, 192 and 195); the packet filter module and the node-engine. | other (the packet filter) |
| The pipeline runner's open branch (rows 190, 193 and 195) gained H-A-326 and H-A-328 at 21:25 in three commits: a step held waiting on a package's publish counts as nothing open for the stalled rule; the seat mesh-builds gains the read verb `published` (module, artifact and fingerprint; answering published, version and digest), served by the builder from a reservation of that fingerprint whose artifact is marked published, or from a kept release of it; and the runner, when it writes a mover's wait on a package, asks it once per package and fingerprint and places the mover at once when the answer is published, the journal saying "placed from the published record" apart from an event; a package published before the pipeline existed thus no longer holds a pipeline until a restart. Two manifests and the seat's definition changed, so the manifest validator runs before the branch's third review; the approved head of row 190 is superseded by this one (rows 190, 193 and 195); the pipeline runner (`mesh-delivery-pipeline`) and the builder. Owed: the answer's time, never filled because the builder keeps no publish time, with that record. | H1's tail (the runner and the builder) |