Answer A-405 and A-406: a node composes around a running build with no entry; the pipeline's manifest passes the judge and is built once by hand

This commit is contained in:
2026-11-14 22:42:00 +01:00
parent 634b4ea49e
commit 4b2eb0bcf4
@@ -951,3 +951,15 @@ the principle that settles it, cited as "design 47 G A-n".
- **A-404** (A-401, A-403; principles 7 and 3) A `source-moved` the gate says for heads it started from the forge, on a new
key or added to a held one, names no group, as A-401's new key does: no group moved it, so nothing times it as a
group's; the key keeps the group a take-in last wrote.
- **A-405** (live, the control-node 2026-11-14 22:34: its node-engine refused every candidate, "nothing provides" postgres-database,
secret, route, s3-bucket, document-server and mcp-endpoint, since its catalogue holds only modules whose wanted build has a
catalog entry, and the providers' wants name the builds running from before G, which have none, their new builds waiting
for a pipeline that cannot be placed while the node refuses; the operator, 2026-11-14 about 22:40: "yes, go ahead";
principles 2 and 7, §421) A module the node runs whose wanted build has no catalog entry stays in the node's catalogue as
the build it runs, from the manifest of that build the node keeps: it provides, claims and requires what that manifest
says, so the node resolves around it. Its want stays held with `entry-missing` (§421) and nothing new of it is composed;
when its new build's entry comes, it is composed as any other.
- **A-406** (live, the control-node 2026-11-14 22:34: the pipeline's manifest at its build was refused by the manifest judge on
2026-11-13, and its candidate carried no parts; the operator, as for A-405; principles 5 and 7) The pipeline's manifest is
made to pass the judge, as any module's; its first build is asked of the builder once by hand, the way a run on request
asks it, since only a pipeline asks builds and none runs yet.