jochen
907051c21d
The review found questions no record decides: 012's minimum-viable-node half and 027's packaging, secrets, sizing and leftovers questions, so both stay active. Where the record lives (006) is issue 414, and 037's two other leftovers are issues 415 and 416; to-be 06 now points at issue 414.
8.6 KiB
status, initiated, touches, became
| status | initiated | touches | became | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| graduated | 2026-08-23 |
|
|
006 — The mesh designed from nothing
What is being investigated
What the mesh would look like if it were laid out today, with the requirements known and none of the accumulated shape — expressed as a skeleton: repositories at the root, modules inside them, and whatever turns out to be the right leaf unit below that.
The deliverables are skeleton.md — tiers, repositories and the four design
moves — and code-skeleton.md — the tier test, what a module looks like on
disk, and where today's catalogue lands.
Why
Every structural decision so far has been a correction: eight contexts replacing thirty-three modules (ADR 0001), domains replacing single-function modules (ADR 0009). A correction inherits the frame of the thing it corrects, and two of the mesh's oldest problems look unsolvable from inside that frame:
- The bootstrap circularity. The mesh needs a database, a bus, a registry and an identity provider. Those are modules the mesh installs. The mesh cannot install them before it exists. This has been worked around repeatedly and never designed away.
- Participation requires privilege. Everything assumes root on a machine whose packages and services the mesh owns. A phone cannot participate on those terms, and neither can a machine someone else administers.
Designing from nothing is a way to find out which parts of the current shape are requirements and which are residue.
And there is more residue than expected, from a knowable source. This began as a
dotfiles repository — the first two days of history adopt dotfiles, add per-node dotfile
overrides, and introduce service symlinking with an ignore file. The flat one-directory-per-tool
catalogue, linking rather than copying, adoption of already-configured machines, per-node
overrides, and the desktop modules are all inherited from that, not chosen for a mesh. Recorded
in 03-DESIGN/00-as-is/10-module-catalogue.md.
That makes this effort's question sharper than "what would we do differently": much of what looks like design is a generalisation of place files on my machines, never revisited because it was never stated as an assumption.
The requirements this is designed against
Stated by the operator, recorded here so the skeleton can be checked against them rather than against taste:
- The mesh manages multiple computers — full control, through modules installed to nodes.
- Mesh state lives in a database: which modules on which nodes, logs, configuration.
- Configuration has several touchpoints — tool surface, web interface, others — all hosted by the mesh itself.
- Connectivity is core: every node reachable from every other over a shared overlay, some nodes publicly exposed, firewalls configured.
- The mesh hosts applications — and requires some of them itself. This is the circularity.
- Arch Linux only for now; ideally any device, including phones, on lighter terms.
- The end goal is to operate an IT company on it — development, design, deployment, full circle, self-hosted. Personal cloud infrastructure.
- Agents make it self-improving and self-healing.
- It is end-to-end testable on one machine (ADR 0016).
Status
A first skeleton exists, with four design moves that the current shape does not have. It was held open because two of them were unproven and one contradicted a record that was already accepted; how each was settled is under What it became below.
Finding worth stating up front: ADR 0001 names nine bounded contexts and none of them owns connectivity — no overlay, no resolution, no firewall, no ingress. Requirement 4 has no home in the accepted decomposition, while research 005 found reachability to be the only part of the catalogue where modules genuinely change together under one intent. The skeleton adds it.
Open questions
| Question | Why it is open |
|---|---|
| Does the record — the event log contexts integrate through — belong to the substrate or the control plane? | It is infrastructure by shape and domain by content. Placing it wrong reintroduces a circularity. |
| One repository per tier, or per context? | Already open from ADR 0001 as "catalogue destination — one repository or many". The skeleton assumes per tier and does not settle it. |
| Answered 2026-08-25 by the operator: a node is a managed machine inside the mesh, not an unprivileged something — and a disconnected node is still a node, in a different situation. The question posed a class distinction; the answer is that there is none, and what varies is state. Recorded as ADR 0004. | |
Answered 2026-08-25 — host-size.md. Measured: the absorption is smaller than the machinery that already applies state, and eight of ten adapters already carry no dependency. The risk is not size but direction, and it is two modules wide. The claim survives with its scope corrected — the host carries one concern, apply declared state on this machine, of which the six are instances. Recorded as ADR 0005, designed in 05-the-node-host.md. |
|
Answered conditionally, which is the honest form — 07-the-foundation.md. The substrate is what the control plane consumes and cannot grant itself. The identity provider qualifies only if the control plane delegates authentication; if it authenticates natively it is an ordinary hosted service. The count follows from a decision not yet taken, and asserting four was asserting that decision. |
|
Does feature survive? |
The skeleton splits it in two and argues the conflation is what makes the delivery pipeline hard to reason about. Unproven. |
What it became
Closed 2026-10-10. The skeleton's moves became decisions and designs, and its open questions were settled by them.
- Where the record lives is not decided. Events became a declared relationship (ADR 0041) carried by the bus (ADR 0106), and the foundation is exactly a store and a bus (ADR 0033, after ADR 0006 and ADR 0028), but no record says what the record is or where it lives. It is tracked by issue 414.
- One repository per tier or per context: ADR 0037.
- Does
featuresurvive: no. ADR 0040 defines a module by the software it delivers, not as a bucket of features; artifact became the word for what a build produces. - The answered rows above became ADR 0004 and ADR 0005, and the designs to-be 05, to-be 07 and to-be 08.