From 7843f56522079c1128b4cb1993962c6a80bb7cbf Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:55:43 +0100 Subject: [PATCH] Answer A-201: the assigner keeps a run's candidate graph until the run ends 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 21a0bcb0..cc1d5833 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 @@ -85,3 +85,6 @@ the principle that settles it, cited as "design 47 G A-n". - **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. +- **A-201** (§189, §190, A-160, A-174; principle 7) The assigner keeps a candidate's assignment graph per run (key + `run-`), made when the candidate's revision is heard and dropped on that run's last `pipeline-ended`, as the + indexer keeps the candidate; the gate's `heads-replaced` drops nothing in the assigner.