novox/mesh-controller
Archived
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Say where an answer no notification can give is given; never offer to silence data loss (hq ADR 0258) #147

Merged
mesh-admin merged 1 commits from fix/needs-you-from-the-console into main 2026-10-08 13:20:42 +00:00
Conversation 2 Commits 1 Files Changed 2
+34 -11
mesh-admin commented 2026-10-08 12:56:17 +00:00
Contributor
Copy Link
Copy Source

Follows #145 (merged). Rebased onto main.

  • A "Needs you" with no button ends "from the mesh MCP server; this notification cannot do it." (FromMeshMCPServer, the glossary's word; "console" is retired): start/stop a waiting walk, release/stop a held delivery, stop a stalled one, restart a module's service.
  • Data missing and data shrank offer no Silence answer; their words say to silence it there.

Tests: plain_words_test.go exact words, TestDataLossOffersNoSilence. Do not merge without the operator.

Follows #145 (merged). Rebased onto main. - A "Needs you" with no button ends "from the mesh MCP server; this notification cannot do it." (`FromMeshMCPServer`, the glossary's word; "console" is retired): start/stop a waiting walk, release/stop a held delivery, stop a stalled one, restart a module's service. - Data missing and data shrank offer no Silence answer; their words say to silence it there. Tests: `plain_words_test.go` exact words, `TestDataLossOffersNoSilence`. Do not merge without the operator.
mesh-admin commented 2026-10-08 12:56:54 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-controller@2e6a9b1efc05 — superseded since 2026-10-08T13:32:21Z

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

Group fix/needs-you-from-the-console, in order: novox/hq@39585e3bb2 → novox/mesh-controller@2e6a9b1efc

  • composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

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 3m17s
  • build-agent on the rest running it: sent
  • route-proxy on ace: judging — 0 healthy judging(s) so far

Transitions

  • 2026-10-08 13:03 (new) → proposed (announced): novox/mesh-controller#147's head announced
  • 2026-10-08 13:08 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 13:08 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 13:21 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-08 13:21 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
  • 2026-10-08 13:32 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-controller@2e6a9b1efc05` — **superseded** since 2026-10-08T13:32:21Z **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 **Group** `fix/needs-you-from-the-console`, in order: novox/hq@39585e3bb2ea → novox/mesh-controller@2e6a9b1efc05 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **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 3m17s - build-agent on the rest running it: sent - route-proxy on ace: judging — 0 healthy judging(s) so far **Transitions** - 2026-10-08 13:03 (new) → proposed (announced): novox/mesh-controller#147's head announced - 2026-10-08 13:08 proposed → checked (checked): the verdict names this commit - 2026-10-08 13:08 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 13:21 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 13:21 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 - 2026-10-08 13:32 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin changed target branch from fix/notifications-after-review to main 2026-10-08 13:02:30 +00:00
jschoubben added 1 commit 2026-10-08 13:03:13 +00:00
Say where an answer no notification can give is given, and never offer to silence data loss
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…
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery superseded: a newer delivery to the same trunk took over its walk
Details
mesh/delivery-group group fix/needs-you-from-the-console closed: a member was closed before the group merged
Details
2e6a9b1efc 
A "Needs you" with no button left the operator guessing where to act, and a click
could silence a condition that says data is gone. The place is named in the
glossary's word, the mesh MCP server (hq ADR 0258).
jschoubben force-pushed fix/needs-you-from-the-console from 5baf4b9c5c to 2e6a9b1efc 2026-10-08 13:03:13 +00:00 Compare
mesh-admin commented 2026-10-08 13:08:06 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 2e6a9b1e

  • 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

Run by the build seat on shanks as build-1791464605672578922 (builds --log build-1791464605672578922).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 50 tool(s); 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
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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T12:55:24Z 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-08T12:55:24Z

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
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-controller/cmd/mesh-builder	1.035s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	164.500s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.021s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.038s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.020s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.200s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.084s
ok  	github.com/novox/mesh-controller/internal/broker	2.695s
ok  	github.com/novox/mesh-controller/internal/builder	1.813s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.757s
ok  	github.com/novox/mesh-controller/internal/conditions	2.220s
ok  	github.com/novox/mesh-controller/internal/envfile	1.059s
ok  	github.com/novox/mesh-controller/internal/facts	1.058s
ok  	github.com/novox/mesh-controller/internal/identity	4.684s
ok  	github.com/novox/mesh-controller/internal/inventory	79.078s
ok  	github.com/novox/mesh-controller/internal/lease	17.707s
ok  	github.com/novox/mesh-controller/internal/licences	4.272s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.039s
ok  	github.com/novox/mesh-controller/internal/link	45.995s
ok  	github.com/novox/mesh-controller/internal/lint	2.117s
ok  	github.com/novox/mesh-controller/internal/outward	1.090s
ok  	github.com/novox/mesh-controller/internal/overlay	1.070s
ok  	github.com/novox/mesh-controller/internal/secrets	1.565s
ok  	github.com/novox/mesh-controller/internal/store	3.445s
ok  	github.com/novox/mesh-controller/internal/testbus	1.250s
ok  	github.com/novox/mesh-controller/internal/token	1.017s
**Merge check** at `2e6a9b1e` - `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 Run by the build seat on shanks as `build-1791464605672578922` (`builds --log build-1791464605672578922`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 50 tool(s); 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 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T12:55:24Z 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-08T12:55:24Z 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 --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-controller/cmd/mesh-builder 1.035s ok github.com/novox/mesh-controller/cmd/mesh-controller 164.500s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.021s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.038s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.020s ok github.com/novox/mesh-controller/examples/route-proxy 1.200s ok github.com/novox/mesh-controller/internal/artifacts 1.084s ok github.com/novox/mesh-controller/internal/broker 2.695s ok github.com/novox/mesh-controller/internal/builder 1.813s ok github.com/novox/mesh-controller/internal/catalogue 4.757s ok github.com/novox/mesh-controller/internal/conditions 2.220s ok github.com/novox/mesh-controller/internal/envfile 1.059s ok github.com/novox/mesh-controller/internal/facts 1.058s ok github.com/novox/mesh-controller/internal/identity 4.684s ok github.com/novox/mesh-controller/internal/inventory 79.078s ok github.com/novox/mesh-controller/internal/lease 17.707s ok github.com/novox/mesh-controller/internal/licences 4.272s ok github.com/novox/mesh-controller/internal/licences/adapters 1.039s ok github.com/novox/mesh-controller/internal/link 45.995s ok github.com/novox/mesh-controller/internal/lint 2.117s ok github.com/novox/mesh-controller/internal/outward 1.090s ok github.com/novox/mesh-controller/internal/overlay 1.070s ok github.com/novox/mesh-controller/internal/secrets 1.565s ok github.com/novox/mesh-controller/internal/store 3.445s ok github.com/novox/mesh-controller/internal/testbus 1.250s ok github.com/novox/mesh-controller/internal/token 1.017s ```
mesh-admin merged commit a759ac65a5 into main 2026-10-08 13:20:42 +00:00
mesh-admin deleted branch fix/needs-you-from-the-console 2026-10-08 13:20:42 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#147