From 18feae5df3e6a36884468b83413a7dd24444b38a Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 03:00:23 +0100 Subject: [PATCH] Design 47 H: H-A-74, nothing of the builder changes in H1; the toolchain wait stays Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 33624fdc..73693846 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -298,3 +298,7 @@ Where two preparers disagreed, the chosen one is named. by the assigner for a node whose node-engine does not state `want:version`; no second event. P7. - **A note on placement (02:55):** a developer's `go.work` per module pointing at the H1 worktrees is the build map's placement, whatever small script wrote it; it is not a placement of the developer's own. The lead's reading. +- **H-A-74 (runner-and-assigner developer, 02:59)** H-A-70's builder part is only a reader of the build seats' `bound` + field, now absent from the contracts; the builder has none, so nothing of the builder changes in H1. G §672's + toolchain wait (the state `waits`, its events, tools and setting) is a build's wait for its toolchain, not a want's + hold on another delivery, and stays: §764 names no builder item, and the builder's lines are H2's. P7; ADR 0682 §9.