From 57c140470123b81c6c8b812f17fdb075aaf909aa Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 19 Nov 2026 13:47:33 +0100 Subject: [PATCH] Answer A-488b: the toolchain stays keyed by the artifact's language; every build module declares what its seat-list reader uses Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 37838c75..7db4c9d4 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 @@ -2021,3 +2021,8 @@ the principle that settles it, cited as "design 47 G A-n". reader starts; `mesh-build-node` declares them. (Live 2026-11-19: `mesh-build-node` consumed nothing, its consumer was never made, it could not judge a named asker and handed every TypeScript ask back.) The catalog check that refuses a module following the seat list without them is noted, not built here. +- **A-488b** (A-488, A-488a; principle 3) A-488's ask language is the seat's; the toolchain the runner puts in a step ask + is still read by the artifact's toolchain language (`go`, `typescript`) as A-104 keys it, never by the ask language. + A-488a holds for every build module whose runtime follows the seat list (`mesh-build-go`, `mesh-build-node`, + `mesh-build-image`), and each also invokes the verb that reader calls, `seat:mesh-catalog.seat-definitions`, so its + manifest names all the reader uses. (From the review of A-488 and A-488a, round 1.) -- 2.54.0