Design 25 bus-state: the lead's answer L1, a merged candidate's manifest is newly accepted

2026-11-12 13:20:17 +01:00
parent a45b31fdaf
commit ff30ac166e
1 changed files with 7 additions and 0 deletions
@@ -397,3 +397,10 @@ clause of the record that statement cites, as it was before the move; "§ 12.n"
  23 readers of ADR 0615 §1 and move in the next milestone, queued on issue 1966. The manifest validator still refuses a moved module's subscription to an event
  its owner does not declare. Every other reader moves when its module is next touched. These moves are tracked by
  issue 1966.
+
+## The lead's answers
+
+- **L1** (issue 1966, met three times on 2026-11-12: a merged module's new build waited for its part grant): a candidate's
+  manifest that a merge makes a module's trunk manifest is newly accepted in §1, so the indexer's merge pass says
+  `manifest-accepted` from the verdict it holds even when that verdict was written for the candidate before the merge
+  and is unchanged; a reader that receives it below the revision it holds treats it as a gap (§12.2) (P3, P1).