jschoubben
941b920bd7
Measured live. All four machines run the identical host binary — same digest, installed within eighteen seconds — and at first only one reported a version, which read as a difference where there was none. A machine publishes a report after an apply. The five-minute reconcile publishes nothing, because it is the machine keeping itself as declared rather than answering anything. So a current, idle machine never says, and the mesh cannot tell that from a machine running something ancient. Confirmed by pushing: not reported, then 04a27ca. Enough for the purpose, not enough for the claim. For deciding whether a new declaration field is safe it is sufficient — pushing is what the mesh is about to do, and the answer arrives with the act. For knowing what the mesh runs it is not, and "not reported" is worded as "nobody has asked recently" for that reason. Making a heartbeat carry it would close the gap and would change what a heartbeat is — a bare word that the node is there, deliberately carrying nothing else. Left alone rather than widened in passing.
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.