jschoubben
a2542e51f8
Filed as a to-do. Nothing is broken by it: every machine here is amd64 and reports so, and one architecture is enough for now. When a machine joins, the mesh should collect what it reasonably can about it and refresh that daily. It already asks what a machine can do; what it is made of is the same question one level down. More is already collected than it looks — eight capabilities, the links that face outside, the host version, and on an adopted machine what it holds, what is reachable and the firewall and tunnel it was found with. The architecture and the kernel are in there too, and nothing reads either: measured, all four machines report amd64 and linux, and node show prints the capabilities beside them without printing them. Missing: memory, disk, the processor beyond its architecture, the distribution and its version, virtual or physical, cores, uptime. Several are what somebody wants when deciding where a module goes, and the placement code's own comment already imagines them. Also missing: the refresh. A machine publishes after an apply, and the five-minute reconcile publishes nothing, so the mesh's picture is as old as the last push. Same mechanism 087 wanted. This is the third thing in one day found to be collected and read nowhere, after held resources and the host version. Whatever gets added should say in the same breath which surface shows it, or it will be the fourth. 159 gains the note that the architecture is already reported, so matching an artifact to a machine needs no new fact — only the comparison and a compiler told what to target.
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.