Design 47 G: the lead's answer A-447b (a build is always for one module) #621

Merged
mesh-tools merged 1 commits from design/47-G-lead-answers-39 into main 2026-11-16 10:30:14 +00:00
@@ -1253,3 +1253,8 @@ the principle that settles it, cited as "design 47 G A-n".
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.
- **A-447b** (replaces A-447's "a fetch asked with no `dir` does every Go module of the tree"; the operator, 2026-11-16
about 11:30 CET: "a build is also for a module, not/never a repo"; principles 3 and 7) A build, a step and a check are
always for one module. Every fetch of a build seat names its module's directory; a fetch with no `dir` is refused,
naming its asker, and no step runs on a whole repository. Every caller that asks a fetch with no `dir` today names the
module it builds or checks, in the same change.