Design 47 H: H-A-136 reads the fetched commit's manifests; the key question goes to H2

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 12:43:31 +01:00
parent aca06fc312
commit cf872d91d4
@@ -623,6 +623,6 @@ Where two preparers disagreed, the chosen one is named.
step, and (2) a requirement at the zero version of a package of the same repository (ADR 0573 §2) is "no module of
that path in the fetched tree". A step's workspace holds, beside the artifact's paths and module.json, every
`generated-from` directory an artifact of the module names, and the directory (with its go.mod) of every package of
the same repository the artifact's go.mod requires at the zero version, found by the manifests of that repository's
modules in the catalog revision; nothing else is fetched. The published version of a package of another repository is
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.