From 2c399ac7086802d51819cb80761f929af1420332 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 11:00:04 +0100 Subject: [PATCH] Answer A-447: a Go fetch asked with a module's directory resolves that module and its local replaces alone --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 9 +++++++++ 1 file changed, 9 insertions(+) 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 88091174..f6d070d7 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 @@ -1239,3 +1239,12 @@ the principle that settles it, cited as "design 47 G A-n". with it: the seat definition's `acts` entry for step `pipeline` and its 30-minute bound, the runner's wait `step` value `pipeline` and the wait's `clock-from`, and the tools `runner_waits` and `runner_release`; G-5 §174 and §190 and G-10's lines naming them are replaced by A-446. +- **A-447** (the build source of a Go artifact is its own module and what it loads, ADR 0267 §1; principle 7; the + operator, 2026-11-16 about 11:00 CET: "start the fix") The Go build module's fetch, asked with a module's directory + (`dir`), downloads, resolves and judges the go.mod and go.sum of that directory's Go module alone, and of each + directory its go.mod replaces with a local path, followed through their own replaces; never another Go module of + the fetched tree. A fetch asked with no `dir` (a check of a whole repository) does every Go module of the tree, as + before. The builder names the module's directory on every fetch it asks, not only for a module that names its paths; + the pipeline runner already does. (Live, 2026-11-16: every build and pipeline step of mesh-delivery's assigner, + builder, checker, teller, view and watchman at 901c800c failed on the indexer's `takein` go.mod, which none of them + loads; their fingerprints did not move with #219's fix, so they could never pass.)