From 24a0fc7272a825ca8286fb2fefc87a8ecd8cc1eb Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:14:52 +0100 Subject: [PATCH] Answer A-230: a restore point names the bus names it took 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 4b8f5694..027d03e2 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 @@ -198,3 +198,6 @@ the principle that settles it, cited as "design 47 G A-n". `catalogue.Manifest.Wants` lists them, optional ones included; a reader that means "required, not optionally" (the module graph's `Requirers`, the assigner's halves) tells the optional ones apart by the entry's manifest (`IsOptional`). +- **A-230** (§554, §565, A-124; principle 7) A restore point's `Point` gains `names`, the bus names it took, one per + bus object as `Aside`'s; the recovery module fills it when it takes a point, and the grants part reads + `points[].names` and `asides[].names` from `kept-points`.