From 79d8ec7a5274ac6265690d7b708cf396d2c66cd9 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:03:06 +0100 Subject: [PATCH] Answer A-154: the approval mark's findings scope and id 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 55ce7387..5639d495 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 @@ -574,3 +574,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-153** (§559, E §1; principles 7 and 8) The tool runner resolves a `deliver: new` subscription's key `.` to its subjects with mesh-sdk's `buscompose.EventSubjects`, the one rule from an event name to its subjects (a seat's event subject or the module's); a pattern with a wildcard is refused with `{error}`. +- **A-154** (design 46 approval mark §4, §16, §19; principles 7 and 8) The approval mark's three findings take scope + `machine` and the id `.`, `.` or `.approvals`, escaped as a key's name, with the + subject of the tool runner on that machine, as the runner's first-view findings already do.