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 24a08d69..8d652c12 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 @@ -982,3 +982,11 @@ Where two preparers disagreed, the chosen one is named. and every pin spans every series. The series a module accepts is what its manifest names (the default series where it names none), and the pin is the newest version the registry published for the package path within that series, whether or not a series value holds contents yet. P7, P3. +- **H-A-186 (an imported mesh package is a declared artifact of its module, 20:49)** Met after H-A-183 (20:29): + importers need Go packages the registry never published, because the owning modules' manifests declare no artifact + for them (the builder's `builds`, the bus module's `busgrants`, disk-load's `diskreadings`), and under H-A-183 such + a package stays unpinned and its importer's build fails loud past the bound. A Go package path another module + imports is a declared Go package artifact of its module, so every release publishes it (G ยง370); the owning + modules declare the missing artifacts now, and the catalog's check refuses a manifest whose Go module imports a mesh + package path that no module of the catalog declares as an artifact (the check reads go.mod requires against the + declared artifacts). P3, P5, P7.