jschoubben
0a61531c42
All three halves of the host's link are through seams, and the reply address in the payload is now proved from both ends rather than one — the test asserts the transport's own field held the consumer's ack address by the time the request arrived, so a server that stopped claiming it fails a test instead of letting the reason become folklore. Two things had to be built for the host to hear anything at all: a node's declaration consumer, which only the controller may create, and the enrolment user's inbox, which design 25 §6 names and the composer granted none of. Both were silent gaps — a node with either missing looks correct and hears nothing. What remains is a single piece: something that composes an enrolment user per live token. On the old bus that account is made imperatively through the broker's management API; here there is no management API, so issuing a token has to recompose the server's configuration. It is the only thing between the two links and a mesh raised on NATS from nothing, so 4.1 now says so.
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.