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.
04-ISSUES
The front door for "something is wrong" at the level of the mesh's design or governance. Diagnosis happens here, where the whole mesh is in view; the fix lands in the owning code repository.
What belongs here
| Belongs here | Belongs in the knowledge base |
|---|---|
| The design permits a failure to be silent | How to fix one occurrence of it |
| A documented rule is enforced by nothing | A command that works around it |
| A stated invariant is false in practice | A node-specific quirk |
| The owner is unknown and finding it needs the whole mesh in view | Symptom → fix, once the answer is known |
The knowledge base already holds the operational record and is indexed on symptoms. This folder is not a second copy of it. An issue here is a question HQ must answer; an entry there is an incident someone must clear. An issue whose answer is a general lesson belongs in both.
Structure
NNN-short-name/
00-report.md the symptom as observed, with the evidence; status in frontmatter
01-diagnosis.md the investigation trail, dated, including what was ruled out
Frontmatter, on 00-report.md
---
status: open | diagnosing | located | resolved | wontfix
opened: YYYY-MM-DD
located-in: [] # owning repo(s) or module(s), filled by diagnosis
fixed-by: # pull request or commit reference, filled at resolution
amended-design: # design doc path, when the root cause was a design gap
---
Rules
- Anyone may open an issue. No localisation is required to report one.
- The full flow is playbook
00-META/process/03-issues.md. - Closed issues are never deleted — they are the mesh's symptom-to-component memory.
wontfixis legitimate and requires a sentence saying why.