Answer A-97: a candidate's build is a pipeline step the runner asks of mesh-builds

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:31:38 +01:00
parent 2eb897699f
commit 720cff7271
1 changed files with 6 additions and 0 deletions
@@ -381,3 +381,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `made` (artifact → digest), `kept-on` and `branch`; the assigner `consumes` `mesh-delivery-builder.build.ended`. A
  want's source revision is the one its pass's kept assignment graph revision was computed from (A-67), matched to
  `version-released.source`; `parts` stay keyed `<module>:<artifact>`, the contract's comment corrected to say so.
+- **A-97** (§230, §194, §473, A-84, A-91; principle 7) A candidate's build is asked by the runner as a pipeline step of
+  its own: the runner's asking half asks the seat `mesh-builds` a `build` step naming each entry by fingerprint, and the
+  builder takes that ask (its one entry point for a candidate) and answers the step's end; `StepRun`'s steps stay lint,
+  unit and integration on the build seats. With the candidate coming that way, the builder's watch of the gate's
+  `source` for candidate base merges goes. A kind-3 dependency's `part` is the entry's kind-3 edge, as built in
+  2dc51626.