Design 47 H: H-A-136, what a step's workspace holds (generated-from directories, same-repository zero-version packages)

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 12:36:37 +01:00
parent 40be107a7e
commit aca06fc312
@@ -617,3 +617,12 @@ Where two preparers disagreed, the chosen one is named.
picture holds 1, forever behind. At a branch's take-in the indexer drops every `trunk.*` and `branch.*` object of the earlier forms no record pins and
the old `current` mark (the branch's newest revision is the current one, H §743); said in the journal, counted. The
stale readers' first views then agree. P3, P7.
- **H-A-136 (what a step's workspace holds, 12:38)** Met live at the first pipeline: the Go build module fetches for a
step only the paths the artifact names plus module.json, so (1) the seat generator's out-of-step check for a generated
package finds no seat definitions (`generated-from` points outside the fetched paths) and marks every file out of
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
used as before (ADR 0573 §4). P3, P7.