Answer A-226b: compose-candidate reads a branch revision key and a run key too
This commit is contained in:
@@ -1280,3 +1280,11 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
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.
|
||||
- **A-226b** (completes A-226 and A-167; ADR 0593 §7; principles 7 and 9) The seat `node-engine`'s `compose-candidate`
|
||||
takes three key forms, parsed by one parser in the seat's client (`nodeengineclient`) that every caller builds its key
|
||||
with: a check's candidate `<group>.<heads hash>` (as today), a branch pipeline's revision `<branch>.<revision>` and a
|
||||
run's `run-<id>`. For a revision key the node-engine reads that catalog graph revision's entries through
|
||||
`mesh-catalog.revision` and composes them as the candidate; for a run's key it reads the run's candidate from the
|
||||
indexer's `runs` state. The seat definition's `candidate` input names the three forms. The assigner builds its key
|
||||
with the client's builder, never by hand. (Live, 2026-11-16: main.948's composition step: "\"main.362\" is not a
|
||||
composition key".)
|
||||
|
||||
Reference in New Issue
Block a user