Design 47 G: the lead's answer A-464c (the gate's source moves a head only forward) #657

Merged
mesh-tools merged 1 commits from design/47-G-lead-answers-71 into main 2026-11-17 01:01:11 +00:00
@@ -1482,3 +1482,9 @@ the principle that settles it, cited as "design 47 G A-n".
the gate. "Said so in its log and its record" is its log line (the repository, the branch, the merge and "not made by a
delivery group of the gate") and its `source-moved`, which then names no group; the gate writes no other record for
it. (From the develop of A-464: the gate holds no merge state of its own for such a merge.)
- **A-464c** (A-464; principles 2 and 7) The gate moves a head of its source only forward and only when it changes: on a
`merged`, at its start and through `gate_source_follow`, it moves a repository's head to a merge only when the head it
holds is contained in that merge (through the seat `git`), and it writes no source revision and says no
`source-moved` when the head would stay the same, as on `take-in.taken` for a head a `merged` already moved. A merged
message heard again, late or out of order is so left without effect, said in its log. (From the develop of A-464: a
replayed message moved heads backward, and each merge wrote two revisions.)