Answer A-84: the builder learns a candidate from the run's build step

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:17:35 +01:00
parent 1963baefb3
commit 5b4cbc035c
1 changed files with 5 additions and 0 deletions
@@ -327,3 +327,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  the revision `source` names, which the indexer holds itself; no field is added to `package-published`. For a build
  of another watched branch, kind 1 compares with that branch's newest build, kept as heard in `heard` as
  `branch-build.<module>.<branch>` (the digest `package-published` carries), not with a released digest.
+- **A-84** (§194 and its candidate's-view line, §348, §473; principle 1) The builder follows no candidate: only a run's
+  steps read a candidate's view, so the builder learns a candidate's build from the run's build step ask, which names
+  each entry by fingerprint; it reads each entry through `mesh-catalog.entry` (repository and commit are the member's
+  head) and needs no pull request number, a build being per fingerprint. Its read of the indexer's `candidates` view
+  goes.