novox/hq
3
0
Fork 0
Code Issues 3 Pull Requests Releases Wiki Activity

Adopt the glossary's vocabulary in the mutable design docs

Browse Source 
"control plane" -> controller and "substrate" -> foundation throughout
03-DESIGN, 00-META and the README, with 06-the-control-plane.md and
07-the-substrate.md renamed to 06-the-controller.md and 07-the-foundation.md.
The immutable 02-DECISIONS records keep their original wording (and links to
them are unchanged) — a term retired here may still appear there, which the
glossary explains how to read.

Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
This commit is contained in:
jschoubben
2026-09-16 18:48:52 +02:00
parent f9f48fbbf7
commit 33a00d5656
25 changed files with 233 additions and 233 deletions
Download Patch File Download Diff File Expand all files Collapse all files
03-DESIGN/01-to-be/22-the-work-ahead.md
+4 -4
View File
@@ -34,7 +34,7 @@ after the phases that change its build path are in — not before.
## Phase 1 — the protocol is one thing, and correct *(mostly done: the drift was dead types)*
**Why here.** The Go control plane and the TypeScript SDK disagree about what a grant carries
**Why here.** The Go controller and the TypeScript SDK disagree about what a grant carries
(`consumer` is the module in one, the node in the other). That is exercised by the installer's own
provisioning — the catalogue's database — so it belongs before more is built on it.
@@ -80,12 +80,12 @@ raises gitea and publishes the SDK before the base build. Those close together i
a protocol that agrees, a registry to publish to. Issue 051.
- [ ] 3.1 the store is adopted — raised at genesis, then held as the `postgres` module; one server,
the control plane's records and every module's database in it
the controller's records and every module's database in it
- [ ] 3.2 the broker is adopted — one `lavinmq`, the `/` vhost for the mesh bus, a vhost per
consumer that requires `amqp`; the second server gone
- [ ] 3.3 an upgrade of each, proven: a store the control plane reads from, a broker over the
- [ ] 3.3 an upgrade of each, proven: a store the controller reads from, a broker over the
broker, each with a stated window
- [ ] 3.4 `status` can say the substrate is behind its source, which today it cannot form
- [ ] 3.4 `status` can say the foundation is behind its source, which today it cannot form
**Done when.** A mesh built from bare metal runs one postgres and one lavinmq, and can upgrade
either — so the twelve-module floor has no specialty left in it.