jschoubben
e05825a881
Versioning: additive is free; a breaking change is refused while callers are bound, and the refusal names them, because the mesh already holds the uses graph; a real break versions the subject, not the seat name, so the role does not fork; binding is a recorded pin, not a drift to whatever is newest. Semantic change stays open — no fingerprint sees it, and saying so beats implying the check is complete. Provisioning: a provisioner's create/remove/holds IS a serves protocol, so a provision interface is a seat that also delivers a credential — which is why design 26 already allowed that. The per-consumer resource is what stops the two collapsing into one. Secrets: sealed, so the bus is never trusted with plaintext — but sealed is not enough, because a stream persists and a durable ciphertext is an archive the day a key leaks. So a secret never enters a stream: core request/reply only, and a declaration names a secret rather than carrying one, which is 0098's fetch-don't-store applied where carrying is worst. The vault's own credential and the bus's own accounts are the two bootstrap exceptions, resolved the way 0067 resolves the control plane. Also rewrote the addresses paragraph, which was too compressed to follow: on-bus addresses disappear because nothing stores them, off-bus ones are untouched and still 0098's problem, and the bus's own address is the one that cannot be a subject.
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.