From b951ffadcadbaa8a04c1f1b3237008f7426f14df Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 23:09:46 +0100 Subject: [PATCH] Design 47 H: H-A-209, a take-in again is an indexer-owned revision --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 7220e629..94c44982 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -1126,3 +1126,11 @@ Where two preparers disagreed, the chosen one is named. answers a tool `indexer_take_in_again {repository}` that takes the repository's current source revision in again (a new catalog revision; moved fingerprints move as at any take-in), so a rule change reaches every repository without a merge made for it. P1; tools-are-how-a-module-is-spoken-to. +- **H-A-209 (a take-in again is an indexer-owned revision, as a re-pin is, 23:09)** Met in the build of H-A-208: a catalog + revision is named after the gate's source revision, a kept source taken in again recomputes nothing (H-A-92), and a + take-in needs the gate's call. The indexer already keeps revisions of its own beyond the gate's numbering for a + re-pin on a publish (`..published..`). A take-in again does the same: it re-reads + the repository's module graph at its current merge commit (the kept requirements), recomputes its modules, and keeps + the result as `..again.` on every watched branch holding the repository; movers whose fingerprint + moved get pipelines as a re-pin's do, under the re-pin's call form; the gate is not asked (P1: source revisions stay + the gate's; derived revisions stay the indexer's). P1, P4.