From e89d0ce8306d36364aad9b0c4f9bec770acb528e Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:28:59 +0100 Subject: [PATCH] Answer A-160: a run's candidate from the branch take-in of its members Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index 150af96c..7f8165ab 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -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-` from the + runner's `run-started`, beside `try-`; 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.