jschoubben
033a5d384c
The tool runtime's manifest names the SDK as a git dependency at a pinned commit; its lock file names a sibling directory that exists on one workstation. It builds only because the recipe runs npm install, which tolerates a lock disagreeing with its manifest and re-resolves from the manifest — the one command that hides this. It matters because a lock exists to make a build reproducible and this one describes one machine, and because it is the first thing a fresh mesh builds: the toolchain carries the SDK and everything with code of its own compiles inside it, so a dependency resolved differently on the build machine than on a workstation is a difference in every module the mesh will ever build. And it is about to be copied. Each language's toolchain will carry that language's SDK the same way, so the shape is worth settling before there are four of them. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
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.