jochen
f709e8e0fb
Not every host path names this machine. A system file the mesh owns is at that path on every machine of the kind — the path is the fact. The operator's shared data is already answered as an access. A path inside a container is the software's contract. What is left, and what a node's default layout would replace, is 514: a module's own data, and what the mesh writes for that module. Documents the reservation model as the records already have it — a root per node, one directory per assignment, a placement for adopted data — and the three things nothing states: where the root comes from, what sits beneath it, and the order the 514 are retired in. Stops there deliberately. Changing where a definition looks without moving the data does not fail: the mesh creates the directory, the container starts, the service comes up empty. Retiring these is a data migration with a verification step, module by module, and belongs with whoever can see the machine.
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.