novox/mesh-sdk
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation

Browse Source
This commit is contained in:
jschoubben
2026-09-05 12:44:17 +02:00
parent 4973b69786
commit 9b7817c8ca
8 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -5
View File
@@ -3,7 +3,7 @@
The stable spine a Novox Mesh **module's own code builds against** — the tool it uses to plug
into the mesh, and nothing that belongs to a specific module or to another tier.
It earns its place by **rarely changing** (novox/hq [ADR 0044](https://git.novox.be/novox/hq)).
It earns its place by **rarely changing** (novox/hq [ADR 0039](https://git.novox.be/novox/hq)).
The test for anything here: *if editing it recompiles unrelated modules and it changes often, it
does not belong.* Per-module code (a service's API client, its tool implementations, its
create-a-resource adapter) lives **in the module**, never here — that coupling is exactly what
@@ -25,7 +25,7 @@ The loop is identical for postgres, redis, minio and umami: watch the grants dir
requested grant call the provider's adapter, write the sealed credential, handle withdrawal, and
keep converging (`watch`). That loop lives here. A **module provides only the adapter** — "create
a database", "create a umami site" — which is the volatile, per-service half and belongs in the
module. This is the ADR 0044 line drawn through provisioning: stable loop here, per-service create
module. This is the ADR 0039 line drawn through provisioning: stable loop here, per-service create
in the module.
### `tools` — the tool-serving harness
@@ -45,7 +45,7 @@ own resolved environment.
## What is NOT in it, and where it goes
- **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 0044.)
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.
- **Host synchronisers** — config-sync, ufw config, vhost generation, systemd, health checks →
@@ -83,5 +83,5 @@ the harness's.
Design and decisions are in [`novox/hq`](https://git.novox.be/novox/hq):
- `02-DECISIONS/0044-what-the-sdk-holds-and-refuses.md` — the stability rule this repository is
- `02-DECISIONS/0045-what-a-module-is.md` — a module, and why its per-module code lives in the module
- `02-DECISIONS/0039-what-the-sdk-holds-and-refuses.md` — the stability rule this repository is
- `02-DECISIONS/0040-what-a-module-is.md` — a module, and why its per-module code lives in the module