jschoubben
ddb3980f09
The first account said the declaration carries no resource that would disable the found firewall and that nothing implemented the sentence the flip prints. Wrong: the mechanism is a step in the host's own apply, retireFirewall, and it is careful — it reads back that the mesh's table is loaded before retiring anything, records the forward policies first, and verifies ufw reports inactive afterwards. What is established: ufw was active and enabled two minutes after a flip that reported the node converged with nothing failed; and the machine's record now reads disabled_by_mesh: true, written by a reconcile fifty minutes later that found ufw already inactive because an operator had disabled it by hand. So the step did not take effect and the record says it did. The candidates are named rather than chosen — the step is skipped silently when the apply has any failure, the mesh's table is loaded by a service in the same apply so ordering is open, and the host's detail lines do not reach the journal, which is why this has candidates instead of a cause.
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.