This implements the proposed hq ADR 0293 (hq #310). Do not merge it before that record is accepted. It changes ADR 0264 decision 4, which says every ask can only be dropped. This PR covers part of novox/hq issue 334.
What changes
broker.TheControllersAsk(stream, subject) is true for a message on the accept subject of a seat in seatsTheControllerAsks (node-build-agent, mesh-build-machine), kept in that seat's own work queue.
link.AgainTo delivers such an ask again on its own subject, and only while the worker that gave it up is on the bus. With no worker, the call is refused and the dead letter stays kept. A seat's work queue has one worker per subject, so only that worker takes the ask.
link.DeliverAgain handles the original first, through removeOriginal. It reads the message at the dead letter's Mesh-Dead-Sequence and deletes it only when its subject and stored time equal the dead letter's. A queue deleted and made again numbers from one (the build handover deletes one), so an old sequence can name a live ask, which is left alone. Next it publishes the copy, and last it removes the dead letter. A copy that cannot be published leaves the dead letter kept for the next try, so there are never two in the queue.
DeadLetter.Original and the verb's original answer field say what became of the original.
Every other non-event dead letter is still refused, with a message that says why.
Grants
None change. The controller already publishes mesh.seat.<seat>.accept.> for the two seats it asks and reaches $JS.API.>, which covers STREAM.MSG.GET and STREAM.MSG.DELETE. The grant golden file is untouched and passes.
Not done here: needs a decision
Asks to other seats would need a grant of every declared seat's accept subjects. That contradicts ADR 0264's consequences and ADR 0259 §3 (the asker of a by-caller ask is a fact the server enforces). ADR 0293 rejects it, so issue 334 stays open for those seats.
Tests (internal/link/deadletters_ask_test.go, real bus)
A build ask its worker gave up on is delivered again to that worker on its own subject. The original is gone from the queue, the ask is handed over once, and a second delivery finds nothing. This failed on main with "only an event is delivered again".
A copy the server refuses leaves the dead letter kept and the original gone, and the answer says both. The retry delivers once.
When the queue was made again and the sequence holds a live ask, that ask is untouched and the answer says so.
With no worker, the delivery is refused, and the original and the dead letter both stay.
An ask to a seat the controller does not ask is refused, and so is a build subject on another seat's stream.
I checked that the sequence test and the no-worker test fail when their checks are disabled. go vet ./... and go test ./internal/link/ ./internal/broker/ ./cmd/mesh-controller/ -count=1 pass.
Rollout
This moves mesh-controller only. No grant changes, so the broker node needs no push. DEAD_LETTERS held nothing live on 2026-10-11 01:18 UTC, so the first live proof is the next build ask a worker gives up on.
**This implements the proposed hq ADR 0293 (hq #310). Do not merge it before that record is accepted.** It changes ADR 0264 decision 4, which says every ask can only be dropped. This PR covers part of novox/hq issue 334.
## What changes
- `broker.TheControllersAsk(stream, subject)` is true for a message on the accept subject of a seat in `seatsTheControllerAsks` (node-build-agent, mesh-build-machine), kept in that seat's own work queue.
- `link.AgainTo` delivers such an ask again on its own subject, and only while the worker that gave it up is on the bus. With no worker, the call is refused and the dead letter stays kept. A seat's work queue has one worker per subject, so only that worker takes the ask.
- `link.DeliverAgain` handles the original first, through `removeOriginal`. It reads the message at the dead letter's `Mesh-Dead-Sequence` and deletes it only when its subject and stored time equal the dead letter's. A queue deleted and made again numbers from one (the build handover deletes one), so an old sequence can name a live ask, which is left alone. Next it publishes the copy, and last it removes the dead letter. A copy that cannot be published leaves the dead letter kept for the next try, so there are never two in the queue.
- `DeadLetter.Original` and the verb's `original` answer field say what became of the original.
- Every other non-event dead letter is still refused, with a message that says why.
## Grants
**None change.** The controller already publishes `mesh.seat.<seat>.accept.>` for the two seats it asks and reaches `$JS.API.>`, which covers `STREAM.MSG.GET` and `STREAM.MSG.DELETE`. The grant golden file is untouched and passes.
## Not done here: needs a decision
Asks to other seats would need a grant of every declared seat's accept subjects. That contradicts ADR 0264's consequences and ADR 0259 §3 (the asker of a by-caller ask is a fact the server enforces). ADR 0293 rejects it, so issue 334 stays open for those seats.
## Tests (`internal/link/deadletters_ask_test.go`, real bus)
- A build ask its worker gave up on is delivered again to that worker on its own subject. The original is gone from the queue, the ask is handed over once, and a second delivery finds nothing. This failed on main with "only an event is delivered again".
- A copy the server refuses leaves the dead letter kept and the original gone, and the answer says both. The retry delivers once.
- When the queue was made again and the sequence holds a live ask, that ask is untouched and the answer says so.
- With no worker, the delivery is refused, and the original and the dead letter both stay.
- An ask to a seat the controller does not ask is refused, and so is a build subject on another seat's stream.
I checked that the sequence test and the no-worker test fail when their checks are disabled. `go vet ./...` and `go test ./internal/link/ ./internal/broker/ ./cmd/mesh-controller/ -count=1` pass.
## Rollout
This moves mesh-controller only. No grant changes, so the broker node needs no push. DEAD_LETTERS held nothing live on 2026-10-11 01:18 UTC, so the first live proof is the next build ask a worker gives up on.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
A build ask its seat's worker gave up on could only be dropped, though the
controller already holds the publish on that seat's accepts and the stream
API to remove the original. Asks to other seats stay refused: delivering them
needs a grant ADR 0264 withholds, in the asker's name ADR 0259 protects.
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
Machines
mesh-controller on novox: passed — healthy 3 times over 3m38s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m35s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 3m41s
route-proxy on the rest running it: sent
Transitions
2026-10-11 01:25 (new) → proposed (announced): novox/mesh-controller#219's head announced
2026-10-11 01:31 proposed → checked (checked): the verdict names this commit
2026-10-11 01:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 02:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 02:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-11 02:53 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@ef551fdfb6b2` — **delivered** since 2026-10-11T02:53:22Z
**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
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m38s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m35s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 3m41s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-11 01:25 (new) → proposed (announced): novox/mesh-controller#219's head announced
- 2026-10-11 01:31 proposed → checked (checked): the verdict names this commit
- 2026-10-11 01:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 02:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 02:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-11 02:53 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
A seat's queue made again numbers from one, so an old dead letter's sequence
can name a live ask; deleting by number alone would drop it silently. An ask
with no worker would wait unseen while counted as delivered.
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
read by no module's build: internal/link/deadletters_ask_test.go
Run by the build seat on shanks as build-1791681552254460767 (builds --log build-1791681552254460767).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T01:18:19Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T01:18:19Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- internal/link/deadletters_ask_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.037s
ok github.com/novox/mesh-controller/cmd/mesh-controller 239.484s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.049s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.033s
ok github.com/novox/mesh-controller/examples/route-proxy 1.248s
ok github.com/novox/mesh-controller/internal/artifacts 1.095s
ok github.com/novox/mesh-controller/internal/broker 2.873s
ok github.com/novox/mesh-controller/internal/builder 2.859s
ok github.com/novox/mesh-controller/internal/catalogue 7.730s
ok github.com/novox/mesh-controller/internal/conditions 2.640s
ok github.com/novox/mesh-controller/internal/envfile 1.054s
ok github.com/novox/mesh-controller/internal/facts 1.075s
ok github.com/novox/mesh-controller/internal/identity 5.119s
ok github.com/novox/mesh-controller/internal/inventory 93.848s
ok github.com/novox/mesh-controller/internal/lease 17.717s
ok github.com/novox/mesh-controller/internal/licences 4.612s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.059s
ok github.com/novox/mesh-controller/internal/link 56.750s
ok github.com/novox/mesh-controller/internal/lint 2.410s
ok github.com/novox/mesh-controller/internal/outward 1.090s
ok github.com/novox/mesh-controller/internal/overlay 1.078s
ok github.com/novox/mesh-controller/internal/secrets 1.571s
ok github.com/novox/mesh-controller/internal/store 3.559s
ok github.com/novox/mesh-controller/internal/testbus 1.260s
ok github.com/novox/mesh-controller/internal/token 1.016s
**Merge check** at `f510b463`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**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
- read by no module's build: internal/link/deadletters_ask_test.go
Run by the build seat on shanks as `build-1791681552254460767` (`builds --log build-1791681552254460767`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T01:18:19Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T01:18:19Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- internal/link/deadletters_ask_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.037s
ok github.com/novox/mesh-controller/cmd/mesh-controller 239.484s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.049s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.033s
ok github.com/novox/mesh-controller/examples/route-proxy 1.248s
ok github.com/novox/mesh-controller/internal/artifacts 1.095s
ok github.com/novox/mesh-controller/internal/broker 2.873s
ok github.com/novox/mesh-controller/internal/builder 2.859s
ok github.com/novox/mesh-controller/internal/catalogue 7.730s
ok github.com/novox/mesh-controller/internal/conditions 2.640s
ok github.com/novox/mesh-controller/internal/envfile 1.054s
ok github.com/novox/mesh-controller/internal/facts 1.075s
ok github.com/novox/mesh-controller/internal/identity 5.119s
ok github.com/novox/mesh-controller/internal/inventory 93.848s
ok github.com/novox/mesh-controller/internal/lease 17.717s
ok github.com/novox/mesh-controller/internal/licences 4.612s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.059s
ok github.com/novox/mesh-controller/internal/link 56.750s
ok github.com/novox/mesh-controller/internal/lint 2.410s
ok github.com/novox/mesh-controller/internal/outward 1.090s
ok github.com/novox/mesh-controller/internal/overlay 1.078s
ok github.com/novox/mesh-controller/internal/secrets 1.571s
ok github.com/novox/mesh-controller/internal/store 3.559s
ok github.com/novox/mesh-controller/internal/testbus 1.260s
ok github.com/novox/mesh-controller/internal/token 1.016s
```
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
read by no module's build: internal/link/deadletters_ask_test.go
Run by the build seat on shanks as build-1791681922596207117 (builds --log build-1791681922596207117).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T01:18:19Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T01:18:19Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- internal/link/deadletters_ask_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.039s
ok github.com/novox/mesh-controller/cmd/mesh-controller 243.305s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.068s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.078s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.048s
ok github.com/novox/mesh-controller/examples/route-proxy 1.259s
ok github.com/novox/mesh-controller/internal/artifacts 1.113s
ok github.com/novox/mesh-controller/internal/broker 2.904s
ok github.com/novox/mesh-controller/internal/builder 2.799s
ok github.com/novox/mesh-controller/internal/catalogue 7.390s
ok github.com/novox/mesh-controller/internal/conditions 2.617s
ok github.com/novox/mesh-controller/internal/envfile 1.052s
ok github.com/novox/mesh-controller/internal/facts 1.078s
ok github.com/novox/mesh-controller/internal/identity 4.906s
ok github.com/novox/mesh-controller/internal/inventory 95.832s
ok github.com/novox/mesh-controller/internal/lease 17.731s
ok github.com/novox/mesh-controller/internal/licences 4.456s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.057s
ok github.com/novox/mesh-controller/internal/link 62.135s
ok github.com/novox/mesh-controller/internal/lint 2.381s
ok github.com/novox/mesh-controller/internal/outward 1.097s
ok github.com/novox/mesh-controller/internal/overlay 1.074s
ok github.com/novox/mesh-controller/internal/secrets 1.546s
ok github.com/novox/mesh-controller/internal/store 3.525s
ok github.com/novox/mesh-controller/internal/testbus 1.252s
ok github.com/novox/mesh-controller/internal/token 1.016s
**Merge check** at `ef551fdf`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**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
- read by no module's build: internal/link/deadletters_ask_test.go
Run by the build seat on shanks as `build-1791681922596207117` (`builds --log build-1791681922596207117`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T01:18:19Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T01:18:19Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- internal/link/deadletters_ask_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.039s
ok github.com/novox/mesh-controller/cmd/mesh-controller 243.305s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.068s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.078s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.048s
ok github.com/novox/mesh-controller/examples/route-proxy 1.259s
ok github.com/novox/mesh-controller/internal/artifacts 1.113s
ok github.com/novox/mesh-controller/internal/broker 2.904s
ok github.com/novox/mesh-controller/internal/builder 2.799s
ok github.com/novox/mesh-controller/internal/catalogue 7.390s
ok github.com/novox/mesh-controller/internal/conditions 2.617s
ok github.com/novox/mesh-controller/internal/envfile 1.052s
ok github.com/novox/mesh-controller/internal/facts 1.078s
ok github.com/novox/mesh-controller/internal/identity 4.906s
ok github.com/novox/mesh-controller/internal/inventory 95.832s
ok github.com/novox/mesh-controller/internal/lease 17.731s
ok github.com/novox/mesh-controller/internal/licences 4.456s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.057s
ok github.com/novox/mesh-controller/internal/link 62.135s
ok github.com/novox/mesh-controller/internal/lint 2.381s
ok github.com/novox/mesh-controller/internal/outward 1.097s
ok github.com/novox/mesh-controller/internal/overlay 1.074s
ok github.com/novox/mesh-controller/internal/secrets 1.546s
ok github.com/novox/mesh-controller/internal/store 3.525s
ok github.com/novox/mesh-controller/internal/testbus 1.252s
ok github.com/novox/mesh-controller/internal/token 1.016s
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This implements the proposed hq ADR 0293 (hq #310). Do not merge it before that record is accepted. It changes ADR 0264 decision 4, which says every ask can only be dropped. This PR covers part of novox/hq issue 334.
What changes
broker.TheControllersAsk(stream, subject)is true for a message on the accept subject of a seat inseatsTheControllerAsks(node-build-agent, mesh-build-machine), kept in that seat's own work queue.link.AgainTodelivers such an ask again on its own subject, and only while the worker that gave it up is on the bus. With no worker, the call is refused and the dead letter stays kept. A seat's work queue has one worker per subject, so only that worker takes the ask.link.DeliverAgainhandles the original first, throughremoveOriginal. It reads the message at the dead letter'sMesh-Dead-Sequenceand deletes it only when its subject and stored time equal the dead letter's. A queue deleted and made again numbers from one (the build handover deletes one), so an old sequence can name a live ask, which is left alone. Next it publishes the copy, and last it removes the dead letter. A copy that cannot be published leaves the dead letter kept for the next try, so there are never two in the queue.DeadLetter.Originaland the verb'soriginalanswer field say what became of the original.Grants
None change. The controller already publishes
mesh.seat.<seat>.accept.>for the two seats it asks and reaches$JS.API.>, which coversSTREAM.MSG.GETandSTREAM.MSG.DELETE. The grant golden file is untouched and passes.Not done here: needs a decision
Asks to other seats would need a grant of every declared seat's accept subjects. That contradicts ADR 0264's consequences and ADR 0259 §3 (the asker of a by-caller ask is a fact the server enforces). ADR 0293 rejects it, so issue 334 stays open for those seats.
Tests (
internal/link/deadletters_ask_test.go, real bus)I checked that the sequence test and the no-worker test fail when their checks are disabled.
go vet ./...andgo test ./internal/link/ ./internal/broker/ ./cmd/mesh-controller/ -count=1pass.Rollout
This moves mesh-controller only. No grant changes, so the broker node needs no push. DEAD_LETTERS held nothing live on 2026-10-11 01:18 UTC, so the first live proof is the next build ask a worker gives up on.
Delivery
novox/mesh-controller@ef551fdfb6b2— delivered since 2026-10-11T02:53:22ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
f510b463mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791681552254460767(builds --log build-1791681552254460767).Merge check at
ef551fdfmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791681922596207117(builds --log build-1791681922596207117).