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 f7cde029..b938d302 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 @@ -625,3 +625,5 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | 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, H-A-230 and H-A-231: every manifest's old-section entries are asked for, never orphans; the keeper keeps, grows and rebuilds only those it made, and creates none (the grants part makes the rest); in build in the bus module. Ten of the eleven clear; the lower-case events stream, which the keeper made under a name the grants part does not derive, stays an orphan, to be dropped on the operator's warrant. | 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 | +| The bus module's orphan judgement (row 106) was fixed, reviewed in two rounds (the first found the keeper taking into its care a state's object store the grants part made, and its cap sum dropping kept state buckets) and merged at 02:33; its take-in took close to three minutes while the indexer waited on a package's versions, where the night's others took under a minute; its pipeline waits with five others on the validate fix reaching the node that runs the holder of the seat mesh-wants (row 107); the bus module and the runbook. | H1 | +| Every take-in of the catalog repository since a Go module was removed from it on 2026-11-17 said "its packages are not published": the indexer (`mesh-delivery-indexer`) lists a repository's packages from its kept packages state too, which still holds the removed module, so the forge's listing of the whole set fails, and the indexer's one-directory fallback runs only on its own error, not on the forge's. Nothing of that repository was published since, so the digests of its three same-repository packages froze on their last commit, and a change to one would not move its seven importers, unsaid; met twice tonight before it was read (row 81 on the pins kind; issue 1585, one release for a change across repositories); the indexer and the forge module. Settled by H-A-232 (a repository's packages are those in the merge's tree, and a gone key is dropped and said; the forge answers not-found and the fallback runs on it; any other failure stays loud), in build in the indexer and the forge module. | H1 |