Design 47 H: H-A-108, the validate step's run, input, baseline and verdict

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 04:10:33 +01:00
parent 0f8c0812d9
commit 9c7fa01851
@@ -462,3 +462,10 @@ Where two preparers disagreed, the chosen one is named.
- **H-A-107 (runner developer, 04:09)** The pipeline value keeps `superseded`, the modules a newer queued take-in took out
of it (written with the movers by compare-and-set; a C-R5 field of the seat, the contracts' writer); at the pipeline's
placing the runner writes a mover's build-step why from it (H-A-53). P1, P4.
- **H-A-108 (assigner developer, 04:10; the validate step)** All four as recommended: (1) the revision's validate run is
a key `<pipeline>.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
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).