From 38fdb88994cc318ebf2f5b03cf77477d1f6d78ce Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 04:10:58 +0100 Subject: [PATCH] Design 47 H: H-A-108 in the glossary's word Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 9aae747e..895701e9 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 @@ -465,7 +465,7 @@ Where two preparers disagreed, the chosen one is named. - **H-A-108 (assigner developer, 04:10; the validate step)** All four as recommended: (1) the revision's validate run is a key `.validate` of the state `composition-runs` in the CompositionRun form with no machine, taken up at start like the composer's runs (P1, P7); (2) the validator's request carries no predefined key list and no known - package names until a design line names the verb that gives them: the judge takes every fallback as declared and + package names until a design line names the verb that gives them: the validator takes every fallback as declared and judges no package name (P7); (3) "a manifest the revision alters" is judged against the branch's previous revision, read through the seat mesh-catalog's verb `revision` (P1); (4) one run, one verdict per revision: every mover's validate step ends the same, failed with `manifest-refused` naming every problem of the revision (P3).