From 2ecb831355a4cb09231693ecb3d82457b7673fa8 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 00:46:04 +0100 Subject: [PATCH] Answer A-453a: a have mid-move is not 'no longer held' --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 208740f0..ffde4ad8 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1323,3 +1323,7 @@ the principle that settles it, cited as "design 47 G A-n". 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`.) +- **A-453a** (A-453, ADR 0539 §16; principle 3) "No longer held" in A-453 means the have has moved past the hold: running, + removed, or at another fingerprint. A have in the middle of a move (`backing-up`, `applying`, `checking`) is not "no + longer held", so the backup ask stands while the node backs up again after an "again" answer, and a second failure + is asked under the next number, as §16 says. -- 2.54.0