jschoubben
9de25994e9
The mesh asserts three things are callable and has never checked any of them. A module on every machine serves an endpoint of its own and dials every other machine's, from the position the callers are in — not the host and not the control plane, both of which reach those addresses by paths no ordinary caller uses and would have passed throughout the outage. Its probe is its own endpoint, declared reachable over the private network, so it is admitted by exactly the rule that governs every internally-exposed service. The tempting target is a service every machine has, and those are the ones never closed — ssh above all — which would have passed for all eleven hours. Resolution and connection reported separately, because they have different owners. One failure is not a fault, and the count travels with the result. It reports and repairs nothing. Built on a scheduled container, a rendered roster fact and a bundle: no new vocabulary. Adopted on its own merits, which is what 0143 was not.
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.