From 2f5268d97a2c9deb59cb2168f7c700d449434490 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:47:38 +0100 Subject: [PATCH] Answer A-187: the consumer ledger keeps a message's first delivery time 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 097aa54f..37de8ef0 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 @@ -28,3 +28,6 @@ the principle that settles it, cited as "design 47 G A-n". - **A-186** (A-179; principles 3 and 7) `conn.AnswerSeat` takes the seat's definition from its caller, which reads it from the seat list it already follows; a verb the definition does not hold, or a definition not yet read, is refused for every caller and said so, so a holder answers only once its seat list is read. +- **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.