Answer A-188: a take-in writes its entries into the gate's record

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 2f5268d97a
commit 92709ec311
1 changed files with 3 additions and 0 deletions
@@ -31,3 +31,6 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-187** (A-176, §76; principle 3) The consumer ledger keeps a message's first delivery time: a message delivered
  again (asked again, or after a restart) keeps the time it was first delivered, so a message that never settles
  grows old and §76's check fires for it.
+- **A-188** (A-172, §170, §151; principles 3 and 7) A take-in writes its entries (each with its module) into the
+  gate's record, so `recovery-merged`'s `module` is filled from the record; no forge-made open path is built, since
+  G ends the mark (§151). A record of the old milestone form, made before G, says no branch.