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 03defe6c..952668ca 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 @@ -790,3 +790,14 @@ The lead's one-line answers to the questions H2's develop and review raise (impl refuses what it does not know). Delivered on its own before H2, as the smallest change of main; the baseline-words mechanism the engine has (ADR 0614) is the thorough shape for the indexer, noted for H2b. design-it-as-it-should-be, P-failure-loud (the validator still refuses; only the read that must survive a new word is lenient). +- **H-A-466 (the node-engine composes nothing of a package artifact, 06:30)** A fault of the node-engine met twice tonight + (the indexer 0.1.110 and the forge bridge 0.1.49 on the control node, both wanted and refused): its resolver asks a + digest for every artifact of a build, a package artifact included, though a package is a build input published to a + registry and never placed on a machine (the SDK says so of ArtifactPackage), and it knows no registry seat for the + kind. The engine leaves package artifacts out of what it resolves, holds and takes in (lookUp, partsMissing, buildOf, + takein.Built, and the artifacts it hands to Resolve), so a want names a digest for every artifact the node places and + none for a package; the registries keep publishing packages as before (H-A-186, H-A-188). Delivered on its own before + H2's group as the smallest change of the node-engine repository's (`mesh-host`) main (the engine's own manifest declares no package, so the running + engine composes the fixed one); the node-engine's H2 branch (`mesh-host` feat/47-H2) then carries main. The ordering edge (the fixed engine before any + module with a package artifact) is a node-engine capability the delivery plan derives, noted for H2b. + fix-a-bug-met-twice, P-failure-loud, design-it-as-it-should-be.