jschoubben
594ea10b07
Found in the lab, doing the ordinary thing: raise a first node, enrol it, send it a declaration. Both declared resources applied correctly and every container on the machine was removed -- the store, the broker, and the control plane that had sent the message. The link died mid-sentence because the broker carrying it had just been torn down by what it carried. Nothing is behaving incorrectly. Apply removes what the store holds and the declaration does not name, which is what reconciliation means. The fault is that the carried bundle and mesh declarations share one store, so the host cannot tell what this machine raised for itself before there was a mesh from what the mesh told it to have. It is invisible until those two meet, which happens exactly once per mesh: on the first node, after enrolment, the moment the control plane first speaks. The report says what is not the answer, including the tempting one -- having the control plane send the substrate back. It cannot: it was never told what the bundle contained, and the bundle exists precisely because there was no control plane to ask.
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.