From 80745b3e020622cac5fceebd7fdedcda1624013c Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 00:00:32 +0100 Subject: [PATCH] Design 47 H: H-A-379, an install's end names the step install --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 6 ++++++ 1 file changed, 6 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 5ecea169..fc060a11 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 @@ -2369,3 +2369,9 @@ Where two preparers disagreed, the chosen one is named. validator in mesh-catalog (the finding-events binding's cap 8 MiB, drop-oldest, the setting findings-max-age with its 7-day default), and the catalogue's module.json rows carry them. The mesh-catalog developer builds the validator rule with the rows; the mesh-sdk developer closes S8 as built. A rule states how it is checked (hq), P9. +- **H-A-379 (an install's end is a step-ended naming the step install, 00:03)** H-A-367 (4) and §800 give the Node + build seat an install whose end carries the archive object's name; the build-step part's step enum knows lint, unit + and integration, and the delivery SDK refuses a step-ended naming another. The step enum and buildstep.PipelineSteps + gain `install`: every pipeline ask ends in a step-ended naming its step, one way, and the archive object's name rides + the install's end as §800 says. The contract part (mesh-contracts, regenerated) and the delivery SDK's check change + together in the group; the Node build module's install answers it. P3.