From 9a90bec9519d188cd9610ed3a7eaf8588c89d127 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 04:59:12 +0100 Subject: [PATCH] Answer A-153: a subscription's key resolves through mesh-sdk's EventSubjects 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 9a409873..55ce7387 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 @@ -571,3 +571,6 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **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. +- **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}`.