jschoubben
6bcf0e4f9f
The store records where each resource came from and each origin removes only its own. Verified on the scenario that caused it -- eleven resources raised, enrolled, sent the same two-resource declaration, and the store, broker and control plane were all still running. A later declaration dropping a resource still removed it, so removal by omission survived the fix. Two more faults found while fixing it, both the same shape. A report published to a routing key nobody bound vanishes: the broker accepts it, finds no queue, drops it, and tells the publisher nothing -- so nodes announced what they had applied into a void. And publishReport was discarding its error, so a node that could not tell the mesh looked exactly like one that had. Reports are mandatory now, so an unroutable one comes back and is said out loud, and the binding covers every key a node may publish.
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.