Answer A-160: a run's candidate from the branch take-in of its members

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 644a9484ab
commit e89d0ce830
1 changed files with 5 additions and 0 deletions
@@ -596,3 +596,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-159** (§466, §472; principles 3 and 7) A build's `resolved{package, version, digest}` names what was used: its
  `version` is the commit the ask names, and its `digest` the sha256 of what was laid (the Go module cache zip, the
  npm tarball), or the member build's digest when it was laid from `builds`.
+- **A-160** (§64, §190, §321, A-85, A-93; principle 7) A run's candidate is keyed by its run id `run-<id>` from the
+  runner's `run-started`, beside `try-<n>`; each member {module, commit, branch} maps to its repository by the
+  registrations and to the branch's revision view as its trunk; its manifests and fingerprints come from the same
+  branch take-in the indexer computes for any commit (its files read through the seat `git`), so no checker preview
+  is heard.