jochen
d497b37e43
The symptom arrived diagnosed as "the registry disabled anonymous pulls for the whole vendor namespace". It did not hold: sibling repositories in that namespace pull normally, the "$disabled" token field appears on every repository including working ones and describes signing rather than access, and "actions": [] with a 401 is byte-identical to what an invented repository name returns. Both registries' own APIs establish deletion instead. Recorded because the correction is the expensive part to rediscover, and because the instance was harmless while the standing condition is not: no node that does not already hold the images can ever provision the module again, and nothing detects that until one tries. Research 015 scopes the replacement. It is not a redesign — the foundation design already commits to S3 the protocol rather than the product, and the object store is an ordinary module, so this instantiates an existing principle. The live OIDC wiring is the requirement that gates the choice, and it is checked first.
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.