From 79214618f333bd841cd1e2f62c68aa0a293165ee Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 13:44:23 +0100 Subject: [PATCH] Answer A-449a: the indexer pins a take-in's revision for its pipelines when it keeps it --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 cf8c8f97..1cb6e388 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 @@ -1276,3 +1276,7 @@ the principle that settles it, cited as "design 47 G A-n". pins its catalog graph revision as a delivery record does: the runner says the seat `mesh-delivery`'s `pinned` when it starts a pipeline and `freed` when the pipeline ends, under the record id `pipeline.`, so the indexer keeps the revision while any pipeline runs on it. No new mechanism; who may say them is a grant of the runner's account. +- **A-449a** (completes A-449; principles 3 and 7) The indexer pins the revision a take-in made for each pipeline the + take-in starts, under `pipeline.` (`..` of each entry), in the same write as it keeps the + revision, so no later take-in can remove it before the runner hears of it. The runner's pin at a pipeline's start stays + (a set: saying it twice is harmless) and its `freed` at the pipeline's end removes it. -- 2.54.0