From 644a9484abfcfcb0d16091f5cc355fc2c6137d40 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:17:41 +0100 Subject: [PATCH] Answer A-159: resolved names the commit and the digest of what was laid Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 3 +++ 1 file changed, 3 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 bbb4c91c..150af96c 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 @@ -593,3 +593,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-158** (design 46 approval mark §16, §677; principle 8) A marked call's answer is `{answer, approval}`: the tool's own answer and the line naming the approval, the form a process holder's `gated-ended` has, so a caller reads one form from both gates. A-157's bound key lives in the runner's state `bound` as `.unanswered.`. +- **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`.