From 81de0c9e3b93ceeed029ba0f8bb342c4c3a7ae23 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 23:49:22 +0100 Subject: [PATCH] Design 47 H: section 10, finding 92 --- .../01-to-be/47-milestones/H-deliver-the-delivery-system.md | 1 + 1 file changed, 1 insertion(+) 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 70dac9cd..0f8a36a9 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 @@ -608,3 +608,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | The pin kind (rows 62, 66, 72, 79, 81 to 85, 87, 88) was fixed one instance per round for five hours, against the rule "at the second failure of a kind, fix the kind"; the rule was then written whole as a specification with a gap table against the code ([H-pins-spec-and-gaps.md](H-pins-spec-and-gaps.md)): 35 lines, 24 built, 6 built otherwise, 1 contradicted, 2 missing, and 7 changes still missing (its section 8), the largest that a re-pin on a publish never became a revision or a mover (the "entry-missing" holds on wants), settled by H-A-211 (a re-pin is taken in as the next catalog revision of the same source); the indexer (`mesh-delivery-indexer`), the pipeline runner, the builder and the Go build module. The lesson for playbook 07: a kind met twice gets its specification before its third fix, and one owner across every part it touches. | H1 (the way of working); H2 for the owed items of the specification's section 8 | | A catalog revision's number equalled the gate's source revision by habit, so a re-pin had no number to keep its entries under, and the pipeline runner started a pipeline per published artifact (several per release) from its own hearing; the indexer (`mesh-delivery-indexer`), the seat mesh-catalog's definition and the pipeline runner (`mesh-delivery-pipeline`). Settled by H-A-212 and H-A-213: a revision's number is the indexer's own counter, with the gate's source as a field; a revision carries its call (`call`: take-in, release of a module version, or take-in again of a repository); one pipeline per release revision; the runner keys pipelines and reads revisions by number. The call's kind is a field of its own, `call-kind`, an enumeration the seat's schema validates (take-in, release, take-in-again), with `module` and `version` or `repository` beside `call`, the words for a person, so no reader parses words (H-A-215). In build by the one owner of the pin kind (row 89). | settled in H1 once delivered | | With revision numbers no longer the gate's source (row 90), two readers still looked a revision up by its source: the seat mesh-catalog's revision verb's source input, and the indexer's freeing of a pipeline's pins on the seat mesh-wants' pipeline-wanted, which named only the source; and the take-in again could re-read only the trunk, since only its merge commit is kept; the indexer (`mesh-delivery-indexer`). Settled by H-A-214 (pipeline-wanted names the revision number; the verb's source input answers the take-in's revision; the take-in again covers the trunk, and another watched branch is re-read at its next merge). In build by the pin kind's second owner: the first ran out of context after the indexer's part, and the hand-over cost one review round. Owed: a take-in again of another watched branch, once branches live longer. | settled in H1 once delivered; H2 for the owed item | +| Beyond the publish re-pin, three more whole recomputes of the indexer (on a build module's assignments change, on a toolchain report, and by the recompute tool) moved fingerprints with no kept revision, and the assigner (`mesh-delivery-assigner`) derived a pipeline's source from its key, which now carries the revision number; the indexer (`mesh-delivery-indexer`), the pipeline runner and the assigner. Settled by H-A-217 (any recompute that moves a fingerprint keeps a revision of `call-kind` recompute naming its reason; the runner treats every revision whose kind is not take-in alike, one pipeline for its movers) and H-A-216 (the assigner keeps the source the pipeline's end names and sends it in pipeline-wanted beside the revision). In build by the pin kind's second owner (row 91). | settled in H1 once delivered |