jschoubben
748f95d417
Six merges landed today and the build machine built nothing — no build was requested, refused or failed, because none was asked for. Asked what was wrong, the mesh said every module was current with its source. All six had moved. The trigger is not broken; there is no trigger. One repository still carries a forge webhook aimed at a port belonging to a different service, and the rest carry none. The intended shape is decided and unbuilt: the forge emits that a pull request merged, the build machine reacts. The forge's module already declares the event; the build machine consumes nothing. Recorded with the question that outlasts the fix — "current with its source" compares what was built against what the mesh was last told, so it agrees with itself and can only ever agree. Whether the trunk moved is a question the forge answers, and an overview that cannot ask it should stop claiming to know.
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.