Design 47 G: the lead's answer A-453 (a backup ask only for a failed backup) #638

Merged
mesh-tools merged 1 commits from design/47-G-lead-answers-52 into main 2026-11-16 23:37:42 +00:00
@@ -1317,3 +1317,9 @@ the principle that settles it, cited as "design 47 G A-n".
own composition or no module could be composed at all. (Live, ace 2026-11-16 23:11: the node refused its whole
composition on ten unanswered requirements, eight of them of modules already staying on their builds with
`entry-missing` or no part digest, so the tool runner's released build 7df8e170 (`node-tools`) was never composed there.)
- **A-453** (ADR 0539 §16, §541; principles 3 and 1) The operator is asked about a backup only when a backup failed. Every
other hold the node-engine writes in a have (an entry asked or missing, §421; parts that differ; a kept data's form
not known) carries its `wait` with step `compose` and its reason, as §541 says; a hold for a failed backup carries
none. The assigner raises the backup ask of ADR 0539 §16 only for a held have with no `wait`, and withdraws a backup
ask whose have now carries one or is no longer held. (Live, 2026-11-17 00:32: the assigner asked "The backup of avahi
failed on ace" and the like for about forty modules held only for `entry-missing` or `entry-asked`.)