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
This commit is contained in:
2026-11-19 13:47:33 +01:00
parent 686bff9021
commit 57c1404701
@@ -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.)