From 8e767e10fb6648a65e47f6562b3e97a45da1f31b Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:55:31 +0100 Subject: [PATCH] Answer A-200: a record joins its take-in by its milestone 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 01797517..21a0bcb0 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 @@ -82,3 +82,6 @@ the principle that settles it, cited as "design 47 G A-n". - **A-199** (A-185, A-193; principle 7) mesh-sdk's `ProcessReader` gains `AdoptEvent(seat, event, hear)`, a seat event heard on the one subscription with no picture, made at once if no follower made it; meshcatalogclient's `WireCandidatesProcess` adopts `catalog-revision` through it and hands each candidate revision to the hook. +- **A-200** (ยง502, A-188; principles 7 and 8) A taken-in delivery record's `milestone` is `.`, + so the watchman ties a `record-opened` to the `take-in.taken` of that branch and source revision by its milestone; + `record-opened` gains nothing, and a record is covered only by what is late for its own revision's entries.