jschoubben
87f464cc5f
The substrate's store and the postgres module are the same thing. They were two rows only while the substrate was a different KIND of thing — a store raised from a bundle cannot provide postgres-database, so anything wanting a database needed a second server. It is visible on any mesh built today: mesh-store and postgres, two containers, the same image. Which name survives is settled by the naming rule. Where a consumer speaks a protocol the interface is the protocol, and "database" is not a capability. The control plane's own queries use distinct on and on conflict, so the coupling is to postgres and a "store" module would advertise a swap that fails the first time anyone tries it. The broker collapses the same way with a different outcome: amqp IS a protocol that several implementations speak, so amqp is a legitimate provision and lavinmq is one provider of it. So adopting the substrate is not only an upgrade path — it is two rows of a mesh's module list becoming one, twice. And it leaves nothing that is a specialty after the pivot, which is the claim the whole design rests on and is not true today for exactly those two. 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.