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 6ab99af9..70f2e95e 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 @@ -626,3 +626,10 @@ Where two preparers disagreed, the chosen one is named. the same repository the artifact's go.mod requires at the zero version, found by the module.json files of the fetched commit (the same manifests the catalog revision holds); nothing else is fetched. Whether a change in such a directory moves the artifact's key (ADR 0499 clause 4) is a finding for H2. The published version of a package of another repository is used as before (ADR 0573 ยง4). P3, P7. +- **H-A-137 (a root module's `generated-from "."`, 13:05)** Met in the review of H-A-136's build: a module whose + manifest is the repository's root (mesh-contracts) names `generated-from "."` for its generated packages, and "the + generated-from directory" read literally is the whole repository, against "nothing else is fetched". For a root + module the step's workspace keeps, beside the artifact's paths and module.json, the generator's inputs and outputs: + the `seats/` directory the generator reads and the paths of every artifact of the module that names + `generated-from` (the generator's check reads every generated package, and one left out counts as missing). Nothing + else of the root. A module in its own directory keeps that directory, as H-A-136 says. P7, P3.