jochen
999636e2a8
The diagnosis carried a table headed "claims that could not be substantiated", denying a module.json, a digest pin, and an all-zeros runtime digest. All three exist. The table is withdrawn in full and replaced with what is actually true, plus the two claims that remain genuinely unverified rather than disproven. The cause: one repository was searched and absence in it was written up as absence. The catalogue of the mesh being built is a separate repository, not checked out where the search ran, and all four claims were about that repository. Compounding it, the predecessor's object-store module and the one being cut over to were treated as one thing — they are different files in different repositories, one pinning a tag with no sidecar, the other a digest with two container resources. Also corrected in the report: located-in named the wrong repository; the "pins a tag" passage described the predecessor; the open question about pinning by digest is struck, because this module already does and it made no difference — a deleted digest resolves to nothing either way. The section on why nothing broke is now scoped explicitly to the predecessor's machinery. The lesson kept in the record: "zero occurrences anywhere in the tree" is only as strong as the tree searched, and a diagnosis must say which tree. A confident rebuttal of a correct report is worse than no diagnosis — it sends the next person to the wrong place with a written record behind them.
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.