Answer A-430: a want names the module version; the node-engine fetches the artifacts by that version (the operator)

This commit is contained in:
2026-11-15 16:43:23 +01:00
parent ee80b4d84b
commit d2094f657e
@@ -1134,3 +1134,10 @@ the principle that settles it, cited as "design 47 G A-n".
serving when a node runs a build of it that serves the seat or verb and is healthy, from its running statement and
the tool runner's announcement, whatever its version and whether or not the catalog lists that build. The rule says
which build it counted.
- **A-430** (§379, §525, §526; the operator, 2026-11-15 about 16:45 CET: "the artifacts simply carry the module
version of course, why would a module have a version otherwise"; principles 6 and 7) A want names the module and its
released version (and the kept-on node for a kept build), never its artifacts' digests: the node-engine fetches each
artifact the module's catalog entry names under that version from the registry seat that holds it, as the registry
tags it, and the registry's answer is what it applies. §379's digests in the want, and the assigner's check whether
a node's node-engine reads them (`want-parts`), go. A build of another watched branch, which has no released
version, is named by the version the builder numbered it under.