From acd7f1f58858c90e8f1e08d95a1a0fdf1ebe7843 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:57:14 +0100 Subject: [PATCH] Answer A-464b: what makes a merge one the gate did not make, and where that is said --- 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 e8fb2e14..6017f545 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 @@ -1478,3 +1478,7 @@ the principle that settles it, cited as "design 47 G A-n". its answer, and how full the state is against its cap. A take-in asked by hand and never answered is then seen, not guessed. (Live, 2026-11-17 01:39: the catch-up of `indexer_take_in` answered "in takeins.catch-up", and no tool could read that key.) +- **A-464b** (A-464; principles 7 and 3) A merge the gate did not make is one whose `merged` names no delivery group of + the gate. "Said so in its log and its record" is its log line (the repository, the branch, the merge and "not made by a + delivery group of the gate") and its `source-moved`, which then names no group; the gate writes no other record for + it. (From the develop of A-464: the gate holds no merge state of its own for such a merge.) -- 2.54.0