Merge pull request 'Design 47 G: the lead's answers A-448 and A-449 (a take-in names its revision; a pipeline pins it)' (#627) from design/47-G-lead-answers-43 into main

This commit was merged in pull request #627.
This commit is contained in:
2026-11-16 12:33:23 +00:00
@@ -1267,3 +1267,12 @@ the principle that settles it, cited as "design 47 G A-n".
Go fetch's one caller with no `dir` is that check, and a fetch with no `dir` still fetches the tree whole for it;
every pipeline step and build names its module (A-447 to A-447c). The refusal of a fetch with no `dir` lands with
the checker's removal.
- **A-448** (§476, §493, §200; principles 3 and 7) `take-in.taken` names the catalog graph revision the take-in made
(`revision`), written by the indexer with the event. The runner starts each pipeline of a take-in at that revision,
never at the revision its own view holds; while its view holds an older one, it waits for it (§200) and places no step.
(Live, 2026-11-16: main.947 was started at revision 356 while its take-in made 357; its composition read 356 after
the indexer had removed it.)
- **A-449** (§153, §579, design 47's "kept while a delivery record pins it or it is current"; principle 7) A pipeline
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.