From 5385c798c0e56dfe89f14949bdd9af08f926e0e9 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 02:08:39 +0100 Subject: [PATCH] Answer A-463a and A-464d: a pending merge is not behind, and every source move is forward --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 9 +++++++++ 1 file changed, 9 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 c390bf97..a4b14ccb 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 @@ -1488,3 +1488,12 @@ the principle that settles it, cited as "design 47 G A-n". `source-moved` when the head would stay the same, as on `take-in.taken` for a head a `merged` already moved. A merged message heard again, late or out of order is so left without effect, said in its log. (From the develop of A-464: a replayed message moved heads backward, and each merge wrote two revisions.) +- **A-463a** (A-463, A-464; ADR 0633 ยง4; principles 3 and 7) A head the source names that the indexer's pending holds + (a merged message waiting for its group's end or its build) is not behind: it is taken in by that path, whole with its + group, and raises no condition. The comparison takes in, through the catch-up, only a head that no pending item holds + and whose taken merge it contains. A source revision heard while a catch-up runs is compared again when that catch-up + ends, so none is skipped. (From the review of A-463: under A-464 the source moves at each member's `merged`, before its + group ends, so a catch-up there took one member of a group in alone.) +- **A-464d** (A-464c; principle 2) Every move of a head of the gate's source is forward only, the move at `take-in.taken` + too: a head moves only to a merge that contains the held head, and a later merge that already moved it is never moved + back. (From the review of A-464c.)