From f062235c5ebcb73861b071c86c79f16c474c471c Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 16 Sep 2026 18:40:40 +0200 Subject: [PATCH] Rename mesh-control -> mesh-controller, substrate -> foundation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit One name per thing, per the HQ glossary: the module/container/image/binary/repo becomes mesh-controller, the seat the-controller, and the store+broker pair the foundation (embedded base bundles, default template and example lock renamed with their go:embed directives). No behaviour change — a pure vocabulary rename. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx --- README.md | 2 +- src/messaging/index.ts | 2 +- test/sdk.test.ts | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d390ef0..90e5101 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ own resolved environment. - **A module's API client and its tool implementations** → in the module. (The Plex client, the Umami client, `tools/plex.ts` — all module-local. ADR 0039.) - **Delivery machinery** — build executor, bundler, dependency resolver, artifact manager, feature - handlers → **mesh-control**. It co-evolves with the pipeline. + handlers → **mesh-controller**. It co-evolves with the pipeline. - **Host synchronisers** — config-sync, ufw config, vhost generation, systemd, health checks → **mesh-host**'s apply engine. The host applies these; they are not module code. - **Domain logic** — tasks, workflows, agents, provider integrations → **tier-2 contexts**. diff --git a/src/messaging/index.ts b/src/messaging/index.ts index 31a7257..ce71883 100644 --- a/src/messaging/index.ts +++ b/src/messaging/index.ts @@ -9,7 +9,7 @@ export type { Envelope, EventHeaders }; /** A request/reply call and a publish/subscribe surface over the mesh broker. */ export interface Broker { - /** Ask one question and await one answer — the client side; the shape mesh-control's command + /** Ask one question and await one answer — the client side; the shape mesh-controller's command * API is reached by. */ request(key: string, body: Req): Promise; /** Answer a question — the server side of request/reply. A tool runtime serves invocations this diff --git a/test/sdk.test.ts b/test/sdk.test.ts index 1caa16d..02dac73 100644 --- a/test/sdk.test.ts +++ b/test/sdk.test.ts @@ -106,7 +106,7 @@ test("modules can SERVE: a real async tool, loaded and invoked over the broker", const broker = memBroker(); const stop = await serveTools(broker, {}); - // Invoke it the way a caller (mesh-control's command API) would — over the broker, by module and + // Invoke it the way a caller (mesh-controller's command API) would — over the broker, by module and // tool, each served on its own key `demo.create_site` (novox/hq ADR 0047). const result = (await invokeTool(broker, "demo", "create_site", { domain: "my-app" })) as { snippet: string }; assert.match(result.snippet, /data-website-id="site-123"/);