Answer A-236: pushed's head and before; groups member gains base

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent b69d526139
commit eba38e5ed9
1 changed files with 5 additions and 0 deletions
@@ -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.<group>.<heads>` with group `run-<id>`.
+- **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.<owner>.<name>.<escaped
+  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.