jschoubben
03fc13b84b
The lavinmq module raises its own server container and provisions vhosts on it, separate from the substrate's mesh-broker. A mesh with the module assigned runs two LavinMQ servers where one belongs — the exact AMQP twin of the two postgres containers. The module's own provisioner already assumes one server: it creates a vhost per consumer, named for the login, isolated by the vhost boundary — the analog of postgres's database-per-login. So the mesh's own control traffic is the / vhost and every consumer's broker is a vhost beside it, all on one server. Adoption therefore means the module does not run a server of its own: its server is the substrate broker, adopted, and the module contributes the provisioner, tools, events and bootstrap against it. The isolation model is already built; what remains to design is only raising the one broker at genesis and then holding it as a module, over the broker it is. 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.