jschoubben
f583502fc9
Both halves had one cause: the mesh knew something and did not say it. Who a consumer is now comes from one derivation, sent to the provider in its grant and to the consumer in its binding, so the two agree by construction. The provisioners use the name they are given and refuse to invent one, because a name of their own would create a login the consumer could never guess while everything reported success. Bound values reach the file that needs them through the symmetric twin of the sealed placeholder — simpler, because they are not secret, so the control plane fills them in and the host gains nothing. The lab run meant to prove this failed in a way that looked like the fix being wrong: rotation could not authenticate against a real database. The cause was the suite rebuilding the control plane's image and not the provisioner's, so an image built that minute ran against a provisioner built the day before. That is 005's family and is recorded with the issue, because the misleading part is worth more than the fix.
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.