From d6318938afc318012d1a8232444c78431982f6a9 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 02:36:56 +0100 Subject: [PATCH] Design 47 H: H-A-69, the gate knows a first-view tool by its name form Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 3 +++ 1 file changed, 3 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 9a28b5cc..87d0dc5c 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 @@ -266,3 +266,6 @@ Where two preparers disagreed, the chosen one is named. - **H-A-68 (node-engine developer, 02:37)** A revert is a want with no `pipeline` and no `rank` (a placement's `build`, H-A-37) naming a fingerprint other than the one running; the applied record keeps no history for it. "Read from the applied record" in H-A-59 reads so: the running fingerprint is what it compares with. P7. +- **H-A-69 (seats developer, 02:38)** How the approval gate knows a module's own first-view tool once the callers env + marker goes: by the tool's name, the forms `_first_views` and `_first_view_again` that mesh-sdk's views + already serve; no environment marker and no tool runner change. P7 (what exists over a new side channel). -- 2.54.0