Answer A-460a: ace's refusal was a hand act; a failed install is tried again when its want changes
This commit is contained in:
@@ -1422,3 +1422,9 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
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.)
|
||||
- **A-460a** (A-460; principles 2, 3 and 7) The versions folder's refusal on ace was a hand act (an immutable mark set
|
||||
2026-11-13, lifted since), not a fault of the node-engine, so A-460 needs no change to its install. A have that
|
||||
failed to install is not tried again on every pass: it is tried again when its want changes (a new fingerprint or
|
||||
version), which is how it leaves a stale failure; the node-engine's want on ace still names an older build, and
|
||||
moves when this change's own pipeline passes (§29). Trying the failed install of that older build again would put
|
||||
an older node-engine on the machine, so no retry is added. (From the develop of A-460.)
|
||||
|
||||
Reference in New Issue
Block a user