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

Phase 1.3 done: ordering was already there, the network was not

Browse Source 
Ordering needed no change for the third time running — resources apply
in the order declared and nothing sorts them — and is now asserted,
because sorting them for any sensible reason would have passed every
other test.

Separates ordering from readiness, which the task had run together: a
container started is not a container ready. Nothing waits, and what
needs something usable retries. That is deliberate and more robust than
start ordering, since a dependency can restart long after apply.

The network was the first thing in Phase 1 that genuinely needed
building, and the first that needed a decision: 0029 records why a shape
rather than an action, and the vocabulary is nine.
This commit is contained in:
jschoubben
2026-08-31 18:55:22 +02:00
parent ce486fd5d2
commit e4327a3a5e
5 changed files with 133 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
03-DESIGN/01-to-be/05-the-node-host.md
+3 -1
View File
@@ -332,13 +332,15 @@ reported to be distinguishable from one that reported an empty list.*
*Written 2026-08-30. Every addition widens what a compromised control plane can express, so the
count is asserted by a test and a change to it is a decision rather than a convenience.*
Six shapes raised the substrate. Two more exist because most of what a person installs is not a
Four shapes raise the substrate. Five more exist because most of what a person installs is not a
service:
| | why |
|---|---|
| **file**, **directory** | the substrate needs neither, and almost everything else does |
| **user** | a shell, a terminal, a chat client, a desktop are a package plus configuration **in somebody's home**. A mesh with no user owns `/etc` and nothing anybody looks at |
| **archive** | a theme is hundreds of files. Inlining them makes every declaration enormous and rewrites all of them when one changes |
| **network** | a module of several containers has to let them reach each other by name, and doing it with an action would create something nothing could ever remove ([ADR 0029](../../02-DECISIONS/0029-a-network-is-a-shape-because-an-action-cannot-be-undone.md)) |
And `file` gained two fields: `bytes`, because a wallpaper is not a string, and `owner`, because a
file in a home belongs to somebody.