From 2829a47ea0fdd102a41e7ad875ad14661255d288 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 17:51:01 +0100 Subject: [PATCH] Answer A-431: a take-in names the source revision it makes, one above the newest seen or said --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 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 43dfbf48..e6ae70d3 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 @@ -1157,3 +1157,10 @@ the principle that settles it, cited as "design 47 G A-n". unreleased"; the `package-published` comparison by digest stays. Order within G: the node-engine's resolution by version first (it unblocks every released build), then the builder and registry tagging; until those land, a want for a branch build keeps its digests for a node whose node-engine reads them, and that form goes with them. +- **A-431** (§476, §493, §648, A-34; live 2026-11-15 17:44: the pipeline runner heard eight `take-in.taken` with no + branch and no source revision, started no pipeline and asked each again for ever; principle 7) The source revision a + take-in names is one above the newest the indexer has seen of that branch (the gate's `source-moved`) or named in an + earlier `take-in.taken`; the gate's `source.` then moves to it (A-34). Every taken event of one take-in carries + the same `branch`, `source` and `entries`, so a reader keyed by branch and source revision (the runner, the gate) + acts once; a taken event that took nothing in (a group's end, one said before G) carries none, and the runner writes + it in its journal and lets it go (§493).