Answer A-279: a member's base is its pull request's base from the forge message

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:37:27 +01:00
parent efcc065f8f
commit 6fc3ccda4b
1 changed files with 3 additions and 0 deletions
@@ -373,3 +373,6 @@ 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 forge
+  message names it (`forgemsg` `base`, said when the pull request is opened or pushed), filled when the gate hears that
+  message, so it is known before any take-in; the take-in's branch never stands in for it.