jschoubben
f52895a646
The store and broker come from a bundle the installer writes once, with images pinned in it, and nothing can change them afterwards: no build, no version to be behind, no roll-out, and no way to report being out of date, because the mesh holds no record of them as modules at all. That is backwards. They are what everything else depends on, so their updates matter most, and they are the only things with no mechanism to deliver one. A mesh with a year-old broker reports itself entirely current. The fix probably already exists: the control plane is carried, raised and then adopted as an ordinary module pinned to what is running. Nothing in that pattern is specific to the control plane. It would also remove a duplication visible on any one-node mesh — the same postgres image running twice, because a store that cannot be a module cannot provide a database to anything. Recorded with the two hard parts stated rather than waved at: upgrading a store the control plane is reading from, and upgrading a broker over the broker. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
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.