Issue 129: three machines of four trust the mesh, not one

Extended after the first was proven. Every converged machine now holds the anchor and verifies an internal name with a plain client; before, the two unassigned ones answered 'unable to get local issuer certificate' and held no entry for the mesh. ace is excluded on purpose: it is adopted, so a module assigned there is held rather than run, which is right and is not trust. Both the resolution and 0147's insight said one machine of four, which was true for about twenty minutes.
2026-09-30 02:30:23 +02:00
parent 5036b927b9
commit d009c3efef
2 changed files with 26 additions and 6 deletions
@@ -139,7 +139,9 @@ written this way until the bed runs.
 > Run on the live mesh because that is where a change is verified now
 > ([ADR 0149](0149-the-live-mesh-is-the-test-bed.md)), and the bed still cannot raise a foundation. The
 > evidence is [issue 129](../04-ISSUES/129-nothing-makes-a-machine-trust-the-meshs-authority/02-resolution.md).
-> It ran on **one** machine; three others still trust nothing of the mesh's.
+> Extended the same day to every converged machine — `novox`, `g14` and `shanks` each hold the anchor
+> and verify with a plain client. `ace` is excluded on purpose: it is adopted, so a module assigned
+> there is held rather than run, which is right and is not trust.

 ## Consequences