Answer A-431: a take-in names the source revision it makes, one above the newest seen or said

This commit is contained in:
2026-11-15 17:51:01 +01:00
parent 09cf7d609d
commit 2829a47ea0
@@ -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.<branch>` 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).