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 b938d302..1f5e9b2c 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 @@ -627,3 +627,4 @@ 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 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 | +| The operator restated at 03:40 the bound ADR 0282 decides: a fix to a leaf module runs healthy on every node within five minutes of its merge, a core module within ten. Tonight's measured parts: merge to take-in 25 to 45 s for the delivery repository and 2 min 40 s to 5 minutes for the catalog repository (cause not yet known; the indexer waited on a package's versions); take-in to placement about two minutes under the queue of pipelines at once; a leaf's build step running past six minutes; and no pipeline reaching its composition since 01:56 (the validate asks). No pipeline completed merge to running tonight, so the whole is unmeasured (rows 85 and 107); the pipeline runner (`mesh-delivery-pipeline`) and the condition keeper. Owed: the pipeline's phases timed and said per pipeline (the pipeline-ended event carries each step's start and end), and the delivery time held against ADR 0282 by a condition. | H2 (the measure); H1 records it |