Design 47 G: §716 (a group's members and bases before the take-in) and the lead's answers A-274 to A-280 #577

Merged
mesh-tools merged 14 commits from design/47-G-lead-answers-10 into main 2026-11-12 12:05:40 +00:00
Showing only changes of commit 6fc3ccda4b - Show all commits
@@ -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.