From e98e6756731ba3fabb615f388d59a2a2b7f33081 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 11:06:14 +0100 Subject: [PATCH] Answer A-275: the node-engine reads invokes with the SDK's one reader Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 5b7eb836..d593d9a3 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -359,3 +359,6 @@ the principle that settles it, cited as "design 47 G A-n". (`mesh.bus..finding-events..`); with no such binding it publishes on the old stream (`mesh.stream..event..`). The module passes no subjects (A-13 holds) and the SDK keeps no foundation list. +- **A-275** (ยง558, A-102; principles 3 and 7) The node-engine's self-composition reads a manifest's `invokes` with + mesh-sdk's `catalogue.readInvokes`, which reads the short and the long form alike; no part keeps its own reader of a + manifest field, and a form it cannot read is refused, never taken as no seats.