Answer A-481a: the composition names its templates archives in a field of its own

This commit is contained in:
2026-11-17 23:39:54 +01:00
parent 7de86e7af9
commit 56b3cd6bc3
@@ -1927,3 +1927,11 @@ the principle that settles it, cited as "design 47 G A-n".
"parts-differ: in the want's parts and not fetched: sha256:5d18d89c...", the digest of `feh:files`, the templates
archive the composer read to render `~/.fehbg`; the composition holds no resource carrying it, so every templated
module with parts was held.)
- **A-481a** (A-481; principles 7 and 3) The composition names its templates archives in a field of its own,
`templates`: the digests ("sha256:...") of every templates archive it was rendered from, sorted, and counted in the
composition's digest as its resources are. It is never a resource: a templates archive is read by the composer and
installed by no apply, so an archive resource standing for it would be a part that is not one. The field is added
where the composition's layout lives (the node-engine seat's contract), filled where the templates are read (the
resolve that holds each built artifact's texts), and read by the node-engine's parts check; one change across those
repositories. (From the develop of A-481: the composition's layout is the seat's strict wire type, and no field of
it fits.)