jschoubben
5042ffd8d3
The loop closed on the workstation: the version landed, the launcher was replaced, the running host stood aside, and after one restart the launcher started a binary the mesh had compiled, published and delivered. The launcher goes as a file resource rather than inside the archive, and that is the safety rather than a preference. A file is written atomically, so the running launcher keeps the inode it started from; an archive writes in place with truncate and would cut a script a shell is reading. The manifest carries a second copy and a test refuses any drift from the one in packaging. Then it would have refused the first declaration it was asked to apply. The Makefile links in two facts the mesh's toolchain does not, on purpose, and one of them is the system the host was built for — read before anything is applied, so the failure is safe and total. Nothing reports it: the unit is active, the bus link is up, and the log says it is hearing what the node should be. Worse, the declaration that would fix it is the declaration it cannot apply, so the mesh cannot repair such a machine. Restored by moving the delivered versions aside and letting the launcher fall back, which is the fallback working as designed. 0142 already settles the version — it comes from where the component sits, not from its linker — and that is unimplemented. The system pin has no answer, and the candidates are a decision rather than a fix: put it in the path too, carry it in a file beside the binary, or stop pinning at link time at all, which is 0005's to change.
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.