From 41dd30fe436e11f6ac183d59171a541b2d997f15 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 15:16:53 +0100 Subject: [PATCH] Amend A-286: a check step that errors after its fetch merged still answers its fetch Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) 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 0c785505..ae7709f5 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 @@ -410,5 +410,7 @@ the principle that settles it, cited as "design 47 G A-n". holds them and a change to them is a changed package. - **A-286** (issue 1921; principle 3) The checker previews and judges every member whose fetch merged, whatever its later steps ended with; only a member whose head does not merge, or whose fetch did not answer, stays - unpreviewed, and the check says which of the two. A failed test never hides the manifest validator or the - composition. + unpreviewed, and the check says which of the two. A check step that errors after its fetch merged (a level that + does not compile or generate) ends failed with its answer all the same: its fetch and the levels so far, beside + its error, so the checker previews from it. A failed test or a failed level never hides the manifest validator or + the composition.