Answer A-201: the assigner keeps a run's candidate graph until the run ends

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 8e767e10fb
commit 7843f56522
1 changed files with 3 additions and 0 deletions
@@ -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 `<branch>.<source revision>`,
  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-<id>`), 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.