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 5127223d..38b1b0ff 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 @@ -1326,7 +1326,9 @@ the principle that settles it, cited as "design 47 G A-n". - **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. + is asked under the next number, as §16 says. "At another fingerprint" applies only to a have that is not held: a held + have names the build it keeps running, which on a failed backup's hold is never the want's, so a held have has not + moved past its hold (corrected 2026-11-17, from the review of A-453's assigner half). - **A-454** (§421's parts check, A-432; principles 7 and 3) A want's parts are the artifacts the mesh built for the module. The node-engine's check that what a composition fetches matches the want's parts counts only what is fetched from the mesh's artifact store (a bundle, an archive, a program, or a container image the mesh built, named through the