From 63dec8f1da98c426753aab6ff12f8975bf793ec9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 01:24:08 +0100 Subject: [PATCH] Design 47 H: H-A-224, a same-repository module named only by a replace is a requirement --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 2eb6fe9a..88030f96 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -1233,3 +1233,8 @@ Where two preparers disagreed, the chosen one is named. it waits or runs: its open steps end superseded (never failed), its running asks are cancelled, the end judgement (H-A-163) counts it as left, and the newer revision's pipeline carries it; a pipeline whose every mover left ends superseded. P1, P3 (the newest truth wins; no work on a fingerprint nothing wants). +- **H-A-224 (a same-repository module named only by a replace is a requirement, 01:24)** Met live: the watchman's entry + still pinned no client the same-repository buildrun module requires, because the watchman's go.mod names buildrun in + a replace directive without a require line, and the reading of the module graph (H-A-201) followed require lines + only. A same-repository module a go.mod names in a replace directive counts as required: its go.mod is read and its + other-repository requirements pinned, transitively, as for a required one. P1, P7.