A mesh seat's holder elsewhere answers before this machine's own provider (hq issue 258) #59

2026-10-05T19:14:17Z

mesh-admin commented

2026-10-05 19:14:17 +00:00

Every machine still runs its own dnsmasq, so each bound ${bound:wildcard-resolution:address} to itself, although mesh-dns-resolver is held (and pinned) on novox. The local-provider branch of Resolve never consulted the seat holder or a pin. Now, for a mesh-wide provision, a pin naming another machine or the seat's holder on another machine wins.

Also carries #58 (the resolver test expects docker to write live-restore), so the controller rolls out once.

Tests: three new resolve tests (fail without the fix); full suite + vet pass against current mesh-catalog main.

Every machine still runs its own dnsmasq, so each bound `${bound:wildcard-resolution:address}` to itself, although mesh-dns-resolver is held (and pinned) on novox. The local-provider branch of Resolve never consulted the seat holder or a pin. Now, for a mesh-wide provision, a pin naming another machine or the seat's holder on another machine wins. Also carries #58 (the resolver test expects docker to write live-restore), so the controller rolls out once. Tests: three new resolve tests (fail without the fix); full suite + vet pass against current mesh-catalog main.

mesh-admin added 2 commits 2026-10-05 19:14:17 +00:00

The runtime's file is the runtime module's: the resolver test expects docker to write live-restore (issue 190, ADR 0196) 853be00ebe

The catalogue moves daemon.json's live-restore and the reload from resolv-conf to the docker
module, so no module writes another software's configuration. The test composes docker beside
the resolver modules and refuses resolv-conf writing the runtime's file.

A mesh seat's holder elsewhere answers before this machine's own provider (issue 258) ce86d09d22

A mesh-wide provision a machine could answer itself was bound to the local provider, with the
seat's holder and any pin consulted only for a provider on another machine. With every machine
still running its own resolver, each bound its resolver configuration to itself while the mesh's
one resolver was held and pinned elsewhere.

mesh-admin merged commit 4b382ceffd into main

2026-10-05 19:14:25 +00:00

mesh-admin deleted branch fix/a-mesh-seat-answers-before-the-machines-own

2026-10-05 19:14:25 +00:00

mesh-admin referenced this pull request

2026-10-06 13:20:08 +00:00

Keep a consumer bound where its data is; only a pin moves it (hq ADR 0232, issue 273) #86

mesh-admin commented

2026-10-06 23:09:46 +00:00

Delivery novox/mesh-controller@4b382ceffdc4 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

tier 0: mesh-controller
tier 1: build-agent
tier 2: route-proxy
ace: receives build-agent, route-proxy
g14: receives build-agent
novox: receives mesh-controller, build-agent, route-proxy
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#59 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-controller@4b382ceffdc4` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#59 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin referenced this pull request

2026-10-08 15:23:43 +00:00

The controller asks the operator and acts on the warrant (hq ADR 0259 §6) #157

mesh-admin referenced this pull request

2026-10-08 16:37:52 +00:00

The controller asks the operator and acts on the warrant (hq ADR 0259 §6) #157

mesh-admin referenced this pull request

2026-10-08 16:41:34 +00:00

Kinded benches, verbs named by their caller, proofs and records (hq ADR 0259 §3) #154

mesh-admin referenced this pull request

2026-10-09 10:38:35 +00:00

Kinded benches, verbs named by their caller, proofs and records (hq ADR 0259 §3) #154