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 9d011375..e40e14ed 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 @@ -628,3 +628,6 @@ 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 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 about 03:33 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 105 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 | +| A release pipeline held the pipeline runner's one slot for nine hours (02:06 to 11:08): its validate ask was lost when the holder of the seat mesh-wants was restarted for a hand pack, and the runner waits on an ask without a bound, so eight pipelines queued behind a step nobody would answer, until the lead cancelled it on the operator's word (rows 107 and 111); the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-235 (every ask the runner makes is bounded, asked again once, then ends could-not-run with a finding, and the slot frees), in build in the runner. | H1 | +| The runner's rerun of a validate step was always refused ("placed no ask now"): the verb looks for the ask by the mover's id, while the validate ask is one per pipeline and names no mover (H-A-51), so a failed pipeline's validate could not be asked again after the pins fix, and proof 1 had to be run a second time from a new merge (row 105); the pipeline runner. Settled by H-A-236 (the rerun of validate asks the pipeline's one validate ask again; the rerun of composition builds the composition ask for the named mover), in build in the runner with the row above. | H1 | +| The bus module's drop and rebuild warrants ask at the destroy level, which needs a code no channel carries yet, so the router held all four of the night's asks unshown ("no channel can carry it now") while the tool answered "the operator is asked", and each expired after ten minutes; the operator saw nothing on Telegram (rows 106 and 108); the bus module and the operator channel's router. Settled by H-A-237 as a weighed bend the operator asked for: the keeper asks at the approve level until a channel carries destroy, with the caller's expiry; the tool reads the router's record and says offered, held or refused; the router's hold reason names the level. Owed: the destroy proof stays designed (ADR 0259), and a channel that carries a destroy answer. | H1 (the bend); H2 (the destroy channel) |