Design 47 H: section 10, finding 108

This commit is contained in:
2026-11-21 02:26:29 +01:00
parent 9d4a013f0f
commit 9bf5b205de
@@ -624,3 +624,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| The validate step's run ask (the manifest validator's program, built and run from the delivery repository's tree) still carried no pins after H-A-203 was built for the test asks, so with the build module refusing a requirement without a pin every validate step ended "could not run" (proof 1's feh at 01:56, the SDK's at 01:30) and no composition followed (rows 81 and 85); the pipeline runner (`mesh-delivery-pipeline`). Settled in H1 by giving the validate ask the pins of the manifest validator's own entry at the pipeline's revision, in build in the runner. The kind: every ask the runner makes carries pins, and a review that reads "every step ask" lists the asks. | settled in H1 once delivered |
| The bus module's keeper reads only a manifest's new-form asks, so the eleven entries the two foundation parts (the artifact registry and the forge) declare in their old sections, all with live data, stand as orphans to it: the registry's incoming store could not be rebuilt empty ("an orphan: drop it, or ask for it in a manifest again"), and the only way to empty it was a drop on the operator's warrant followed by the grants part's assert that makes it again; a careless drop of any of the other ten would lose live data (rows 65 and 104); the bus module. Settled by H-A-229 (the keeper counts an entry a foundation part's old section declares as asked for), in build in the bus module. | H1 |
| Three fixes were merged between 02:09 and 02:13 and each taken in within a minute (the flood halved after the dead upload was dropped): the validate and composition run asks' pins (the holder of the seat mesh-wants), the tool runner's fill from the stream's figures, and the receiver's one read per transfer. The first lands in the holder that runs on a node of its own and through which every validate step runs, so no pipeline can deliver it to itself: a hand pack for that node, copied by the operator at their terminal (the session's permission check refused the lead's copy) and restarted there before the running pipelines' validate steps can pass. The last of the three re-pins twenty-nine modules into one pipeline; the runbook. | H1 |
| The bus module's drop of an orphan asks the operator's warrant with a window of ten minutes, and then ends with nothing removed ("ask again with a new request") while the operator is away, whereas the session's own asks carry an expiry the asker sets (up to a day); the drop's warrant should carry the asker's expiry too, or at least the operator's answer to the session's ask should count (row 106); the bus module. Owed: the bus module's warranted acts take an expiry from their caller. | H2 |