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 fa12f01a..41e99f4a 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
@@ -373,7 +373,7 @@ the principle that settles it, cited as "design 47 G A-n".
   function `AnswerSeat` takes is written once, in mesh-sdk's `seatlist` (the definition of a seat from the list a part
   follows; none until the list is read, none for a seat it does not hold), and every holder passes it. A part that
   serves a seat verb follows the seat list with its grant, as the pipeline runner and mesh-recovery now do.
-- **A-279** (A-236, §715; principles 1 and 7) A group member's `base` is its pull request's base branch as the gate
-  already keeps it in that pull request's delivery (the `base` `mesh-delivery.show` answers, set when the pull request
-  is announced), filled when the member joins its group, so it is known before any take-in; the take-in's branch never
-  stands in for it, and no new event or state is added.
+- **A-279** (A-236, §715; principles 1 and 7; corrected twice) A group member's `base` is its pull request's base
+  branch as the seat `git` says it in `pull-updated` (which carries `Base`): the gate consumes that event and keeps the
+  base in the pull request's entry of its record (`RecordGroup.Pulls`, one field `base`), so it is known before any
+  take-in; the take-in's branch never stands in for it.