From a2f2e5b98df61e78e35b8b7c5985134789d6cc8b Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:35:18 +0100 Subject: [PATCH] Answer A-169: one key form for every holder of pins Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index a8063dd6..704023b4 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -635,3 +635,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-168** (E §33, design 46 approval mark §5; principle 3) For a marked wait on a module the runner does not serve, the marks are the union of the newest entry of every followed branch; where the runner serves the module, its served entry is added to that union. A mark is never lost. +- **A-169** (§579; principles 2 and 7) A pins state keys a revision by the revision object's own name (the assigner's + `trunk.`, the indexer's `.`), value `{records, missing?}`, and holds two more keys in the same + form in every holder of pins: `made`, written once by create-only when the state is first used, and + `pins-stated`, the `at` of the applied event; pins count only once a `pins-stated` later than `made` is applied.