From 92709ec3114c0c3931ebe21d6d8ae9bd435f78a7 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:47:54 +0100 Subject: [PATCH] Answer A-188: a take-in writes its entries into the gate's record Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 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 37de8ef0..f98dcbdb 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 @@ -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.