From eba38e5ed9b90d82df62292f5ed87bfb3f27fa54 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:18:29 +0100 Subject: [PATCH] Answer A-236: pushed's head and before; groups member gains base Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 b4110533..9e1119b6 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 @@ -219,3 +219,8 @@ the principle that settles it, cited as "design 47 G A-n". pipeline it placed for the run has ended, as it says a group's end; the assigner drops its candidate graph on it, and the indexer drops the run's candidate on it in place of counting members itself. The kept object's key stays the seat's form `candidate..` with group `run-`. +- **A-236** (§509, §714, §715, §11, A-227; principles 2 and 7) A `pushed` message's new head is `head`; the bridge + keeps each watched branch's last head written in its own state `heads` (key `branch...`), `before` read from it and its start read comparing with it; `pushed` carries the same take-in inputs as + `merged`. For §715 the mesh-delivery seat's `groups` member gains `base` in the contract, which the gate fills and + the bridge reads.