From ca8cda69d95bf07315b23406bbb11a40c976fd7b Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 11:15:34 +0100 Subject: [PATCH] Answer A-447a: a module whose directory holds no go.mod takes the go.mod files under it; an empty choice fails --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 f6d070d7..d5c93baa 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 @@ -1248,3 +1248,8 @@ the principle that settles it, cited as "design 47 G A-n". 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.) +- **A-447a** (completes A-447; principles 3 and 7) A module's own Go modules are the go.mod of its directory or, when + its directory holds none (a module at the repository's root whose Go code lies in `go/`, a contracts module with a + go.mod per seat), every go.mod under its directory (in a narrowed tree, under its paths); then each one's local + replaces, as A-447 says. A fetch asked with a `dir` that chooses no Go module fails, naming the directory: it never + goes on to steps that would pass with nothing tested or built.