Answer A-449a: the indexer pins a take-in's revision for its pipelines when it keeps it

This commit is contained in:
2026-11-16 13:44:23 +01:00
parent 8fa037074c
commit 79214618f3
@@ -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.<key>`, 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.<key>` (`<branch>.<source>.<module>` 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.