novox/hq
3
0
Fork 0
Code Issues 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/18-building-a-module.md
+4 -4
View File
@@ -24,9 +24,9 @@ why the current model does not fit what a module is.
Turning a module's source into artifacts the mesh can pin, publish and deliver — and saying
truthfully what was produced and what it was produced against.
Everything else is somebody else's: *what* to build is the control plane's, *what a build means* is
Everything else is somebody else's: *what* to build is the controller's, *what a build means* is
the catalogue's ([ADR 0072](../../02-DECISIONS/0072-two-graphs-and-the-build-chain.md)), *where an artifact runs* is the
control plane's again. The builder's whole responsibility is the middle.
controller's again. The builder's whole responsibility is the middle.
## The language
@@ -130,7 +130,7 @@ change is one edit; with four it is four that must land together, and a mesh who
about the envelope fails by ignoring messages rather than by failing to compile.
**So the contracts have to stop being expressed twice before they are expressed four times.** They
are already: the manifest, declaration and link shapes exist as Go structs in the control plane and
are already: the manifest, declaration and link shapes exist as Go structs in the controller and
as TypeScript types in the SDK, kept in step by hand. Nobody has felt it because both live in one
repository. A second *language* makes that drift; a specified envelope and schema that every SDK
implements makes a second language an implementation rather than a translation.
@@ -176,7 +176,7 @@ disagrees with it.
| `certificate` | a certificate for a name it serves |
| `grants` | credentials it must create for its consumers |
| `filtering` | rules beyond its own ports |
| `computed` | marks a module the control plane generates rather than an author writing |
| `computed` | marks a module the controller generates rather than an author writing |
| `build.artifacts` | what it produces |
### What it builds