jschoubben
013dbce4a9
Installing the module that provides `artifact-store` requires something that provides `artifact-store`: its image is mirrored in, mirroring publishes to the store, and the builder refuses to run without one. Never seen, because the lab always has a registry standing before the mesh asks for one, and so does any mesh built on a machine that already had one. What it blocks is larger than a registry. The store holds images and packed archives both — it is the module catalogue in artefact form — so until it exists a mesh can run only what its bundle already carries. The substrate record already answers it. It asks of each candidate whether it can grant itself the thing it provides: the store cannot create its own database, the broker cannot create its own virtual host, and the registry cannot grant itself a repository. So the registry module names its image and is never built. With a limit worth saying out loud rather than discovering: a module providing the store may not build artifacts of its own, a UI or a tool server included, because there is nowhere to put them until it runs. Such a registry is two modules.
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.