diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 3de0573f..74808baa 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1864,3 +1864,13 @@ the principle that settles it, cited as "design 47 G A-n". while a validation ask of any repository is out, since every take-in moves the one revision a request is built from; it still compares the heads and raises A-463's merge-untaken condition meanwhile, and only its take-in waits. `validate-tries` defaults to 3 and is at most 20. (From the develop and review of A-475.) +- **A-476** (the operator, 2026-11-17 ~17:30 CET, from the delivery walkthrough: "no manifest check needed at this + point"; "for each module that is registered in our module graph, for the affected repo -> check the fingerprints"; + the indexer's own-build hold: "this is jibberish"; then "yes" to removing all three; principles 7 and 3) The take-in + is three things only: a new commit on a module's watched branch, the fingerprints of the modules registered for + that commit's repository, and a catalog revision naming the modules whose fingerprint moved. (a) The take-in asks no + manifest validation: validating a manifest becomes a step of that module's pipeline; until that step exists, nothing + validates at the take-in. (b) The indexer takes in with the build it runs, whatever build of the indexer the + revision names: ADR 0633 ยง1's hold and its hand take-in end (withdraws A-475 and A-475a, which tuned that hold's + validation). (c) A commit moves only modules registered for its own repository; no other repository's module is + recomputed by it. A toolchain or build-module change still moves the modules it builds, at the next take-in.