From 19f969b2db1a191255bec0ed6582a0c6a29431ad Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:34:12 +0100 Subject: [PATCH] Answer A-168: marked waits take the union of every branch's newest entry Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 3 +++ 1 file changed, 3 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 36454650..a8063dd6 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 @@ -632,3 +632,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". goes back to an earlier fingerprint, which the assigner computes itself; a kept data's `form` is read from the catalog entry's kept declarations (`catalogue.KeptDeclarations`). AS14's named seat and contribution edge, and AS17's ask of the operator, go to a design line. +- **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.