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 d3a4147c..573627cf 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
@@ -186,3 +186,6 @@ the principle that settles it, cited as "design 47 G A-n".
   `mesh-compose` once per node-engine fingerprint among the machines (the change's build where the change alters the
   node-engine, §63), the program read from that fingerprint's catalog entry through `entry`, each run's request
   joining the inputs of the machines on that fingerprint.
+- **A-227** (withdraws A-221 and A-223; §714, §715) As design line §714 says, a merged message gains `base`, the
+  watched branch it landed on; `branch` stays the pull request's branch and `head` its head commit, as today;
+  `pushed` keeps `branch` for the branch pushed and gains `before`.