From 42054c599cbc6cd7742c65d74d00acae92e571e4 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 11:31:19 +0100 Subject: [PATCH] Answer A-447c: nothing in building, checking or delivering works on a repository --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 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 fb9185f8..7b771a03 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 @@ -1258,3 +1258,10 @@ the principle that settles it, cited as "design 47 G A-n". 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. +- **A-447c** (widens A-447b; the operator, 2026-11-16 about 11:32 CET: "everything in a pipeline should be module + based, not repo-based", "nothing is ever repo-based"; principle 7) Nothing in building, checking or delivering works + on a repository: every part works on one module. What it fetches, lays beside, chooses and runs as tests, computes as + digests, lints, builds, publishes, checks, judges and reports is the module's and what that module loads. A merge + is said for the modules it changes, and only those move. A repository is only where a module's files are fetched + from. A part that reads, chooses or judges anything of another module of the same repository is a fault of that part, + fixed in it.