From c3246cfeb4a3d9958b761a3c316d01971bc5a9b5 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 00:43:18 +0100 Subject: [PATCH] Design 47 H2: H-A-399, the SDK's step parts owner, the install archive via the artifact store, check-needs names seats --- .../01-to-be/47-milestones/H2-lead-answers.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 2637eee4..204b6710 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -237,3 +237,18 @@ The lead's one-line answers to the questions H2's develop and review raise (impl tools-are-how-a-module-is-spoken-to). The contract row is the mesh-delivery developer's (mesh-delivery-contracts, regenerated). §786's "could-not-run" end is read as the pipeline outcome failed (a could-not-run step ends it so); the outcomes stay passed, failed, refused, superseded, cancelled. P3. +- **H-A-399 (the delivery SDK's step parts for §791, §800 and §801; the install archive travels through the artifact + store; check-needs names seats, 00:43)** BM2 to BM5. (1) The shared parts in mesh-delivery-sdk's steprun and buildstep + (ReadGoTest answering not-run from skips opening "NOT RUN:", testStep carrying not-run into the end and the "mesh: + setup starved:" path to again whose third run ends could-not-run, StepAsk carrying an install ask and RunAsk + dispatching it, AskNeeds and Has reading the check-needs field, the step's archive reaching the check job, the outputs + store named `outputs`, the output and current verbs at form 2) are one owner's: a third mesh-delivery developer on the + delivery SDK alone (P3, one owner per file, as H-A-390); the build modules' developer builds against its head. (2) The + install archive moves between build nodes the one way bytes move between them: the Node build module's install + publishes it to the artifact store (the seat oci-artifact-registry) as the module's archive artifact under the ask's + version (H-A-373), and the install's end names that reference; the Go build module fetches it by reference as it + fetches a pinned archive. No new verb, no read of another module's objects (ADR 0596). (3) `check-needs` names the + seats a package's integration tests need the node to hold, as the marker did (`node-build-node`), one value form for + a need (H-A-375 reads the same); mesh-sdk's S10 value `node-modules` is corrected to a list of seat names, a one-line + commit in the mesh-sdk worktree by the build modules' developer citing this answer. RG2 covers artifact-store-tools + as the map says. P-NATS-native, P3, ADR 0596.