Answer A-461a: another node's module is laid from the assignment's placed build

This commit is contained in:
2026-11-17 01:11:09 +01:00
parent e68d3a892e
commit 2ff96d1b7e
@@ -1418,3 +1418,7 @@ the principle that settles it, cited as "design 47 G A-n".
`publish-pause-max`, and after `publish-tries` tries it ends loudly (log, condition) and stays readable in the
builder's tools; all three are settings with defaults (30 s, 30 min, 8). (From the develop of A-457: a work-queue
stream would need a `bus` restating the builder's whole account, or a second process.)
- **A-461a** (A-461; principles 7 and 1) "The build its want names" for another node's module is read from what the
composer already holds for every node: the assignment's placed build of that module on that node (absent meaning
the newest delivered, as the assignment says). The composer watches no other node's wants. (From the develop of
A-461: the composer holds only its own node's wants.)