jschoubben
a9b8f41570
Two corrections of fact, both found by building the module's image and connecting to it as a host would. The first composed configuration said `verify: true`, which makes the server demand a *client* certificate — and nothing in the mesh presents one. A host pins this server's exact certificate and authenticates with the password the mesh minted, and so does a module's runtime. Every connection in the mesh would have died at the TLS handshake before any password was looked at, with an error that reads as a fault in the client. TLS is still required; verify only decides whether client certificates are checked. Mutual TLS is a later question and would need machinery the mesh does not have — a certificate per module per node. And §4 read as though the controller wrote the whole file. It writes the user list and nothing else: ports, TLS paths and a store directory belong to the container the module raises. The two files share one directory of necessity, because an absolute include path is resolved relative to the including file's own directory. The decision stands in both cases — accounts are composed, not called for, and passwords are minted and sealed. What changed is what the file says and who writes which half.
03-DESIGN
The authoritative specification. Implementation is built against what is written here.
Two layers
| Folder | What it is |
|---|---|
00-as-is/ |
The mesh that exists today. Shipped behaviour, described as it is — including behaviour nobody would choose again. |
01-to-be/ |
The mesh being built toward. Every statement traceable to a record in 02-DECISIONS/. |
They are never mixed. A statement about the future does not belong in an as-is document, and an as-is document is never edited to describe an intention.
When a to-be design ships, it does not move. Its as-is counterpart is written or updated,
the to-be document's status becomes implemented, and both stand — one describing what runs,
the other recording what was intended. Deleting the intention loses the reasoning, which is
the expensive half.
Frontmatter
Every design document (not the READMEs) carries:
---
layer: as-is | to-be
status: designed | in-progress | implemented | abandoned
code: [] # owning code repo(s), from 00-META/repos.md
updated: YYYY-MM-DD # date of the last status change, not of text edits
decisions: [] # 02-DECISIONS/ records this document rests on
---
For an as-is document, status: implemented is the normal state — it describes something that
runs — and code: names where that implementation lives.
Status changes when implementation state changes, never because design text was edited. An
implemented claim must be defensible from the owning repository's main branch, not from
intent. If it cannot be checked, it is in-progress.
Cross-cutting views are generated from this frontmatter by the hq-status skill and never
written to disk.
What belongs here
Functional analysis, architectural description, and specification — prose and diagrams
only, no code. A manifest field may be named; a manifest may not be pasted. A document
enters the to-be layer only after the decision behind it is recorded in 02-DECISIONS/
and the research that produced it is closed.
Subfolders are encouraged where a layer grows enough to need them.