From 82c483fccc5f6387d1e4dd8750d61adb7a813b9c Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 04:58:10 +0100 Subject: [PATCH] Answer A-152: the toolchain digest is the sha256 of the program run 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 57af4354..9a409873 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 @@ -568,3 +568,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". group member's build, with a `binds` file as go-package-registry's (`at`, `serves.port`), and read the blob by the store's own path `:/v2///blobs/`; they never write into it, so ADR 0614 §2 holds, and their manifest tests assert the read. +- **A-152** (§472, §492; principles 3 and 7) The toolchain's `digest` is the sha256 of the toolchain program the build + module runs (the `go` or `node` it finds), computed at its start and again when the toolchain's version changes; no + field is added to the provision.