088, 089, 120, 128 and 130 each name a commit that is on main and cites them —
the forge's address following a moved port, a route naming its endpoint, a
provisioner asking the backend what is there, the hosts file written into a
marked block, and undeclaring giving a unit back the state it was found in.
Each says it was closed by reading commits rather than by a run, so nobody
reads a green that was never measured.
129 stays located on purpose: ca-trust is merged and no machine holds it, so
the symptom it opened on is still true everywhere.
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 | wontfixopened:YYYY-MM-DDlocated-in:[]# owning repo(s) or module(s), filled by diagnosisfixed-by:# pull request or commit reference, filled at resolutionamended-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.
jschoubben
14be8576f8