From ef87d14e2718772dc3055cbda3060a92e248f6b5 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 19 Nov 2026 15:45:04 +0100 Subject: [PATCH] Answer A-489c: the build modules' kit also holds that a puller counts the runs that started Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 dec8eaad..362a9fb5 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 @@ -2044,3 +2044,7 @@ the principle that settles it, cited as "design 47 G A-n". module's test runs it, and the catalog's failure-kit check refuses a build module whose tests do not. A step ask is never the first place this is found. `mesh-build-node` has the need `node-build-node` alone, as `mesh-build-go` has `node-build-go`. +- **A-489c** (A-489a, A-489b; principle 3) The same kit holds the count A-489a's poison reads: the build modules' + conformance kit has a case that refuses a puller which does not read the runs that started from its module's own + `steps` state, every build module's test runs it, and the catalog's failure-kit check refuses a build module whose + tests do not. (From review round 3 of the build-node step-ends fix.)