nox works without the controller: each command calls the seat or tool that owns its job (issue 1126) #593

2026-11-02T09:48:47Z

mesh-tools commented

2026-11-02 09:48:47 +00:00

Issue 1126 (design 47): nox (mesh-cli) mostly forwarded to the controller through the node-engine's socket, so with the controller unassigned (2026-11-02 10:09) it answered nothing but enrol. It now calls each job's owner — seat verbs and module tools — through this machine's console (the mesh MCP server node-tools serves on loopback): 77 command lines (status, what runs where, placement as proposals for the operator's Approve, deliveries, conditions, healers, hand acts, config, vault, artifacts, licences, issues, the knowledge base, enrolment), plus generic call, ask, search, describe. The 15 controller lines with no successor say so, name what to use instead and exit 1; nothing claims success it did not have. Command map: hq .work/1126/nox-map.md.

Manifest: requires: mcp-endpoint, file /etc/mesh-cli/console (loopback address only, filled like claude-code's); no account, no invokes; go.mod drops mesh-sdk.

Tested locally (GOWORK=off): gofmt, go vet, go vet -tags integration, the unit suite (a 53-row table against a stand-in console answering like node-tools' mesh_call); the new binary was run against the live console and 13 commands answered.

Known: the comment and one row describe cleanup delete without --confirm as a dry run; the vault refuses instead (harmless; noted on issue 1126).

Reviewed-by: review-g2@shanks at 63de1f7e0d
Pushed-by: lead-47@shanks

https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

Issue 1126 (design 47): `nox` (mesh-cli) mostly forwarded to the controller through the node-engine's socket, so with the controller unassigned (2026-11-02 10:09) it answered nothing but `enrol`. It now calls each job's owner — seat verbs and module tools — through this machine's console (the mesh MCP server node-tools serves on loopback): 77 command lines (status, what runs where, placement as proposals for the operator's Approve, deliveries, conditions, healers, hand acts, config, vault, artifacts, licences, issues, the knowledge base, enrolment), plus generic `call`, `ask`, `search`, `describe`. The 15 controller lines with no successor say so, name what to use instead and exit 1; nothing claims success it did not have. Command map: hq .work/1126/nox-map.md. Manifest: `requires: mcp-endpoint`, file /etc/mesh-cli/console (loopback address only, filled like claude-code's); no account, no invokes; go.mod drops mesh-sdk. **Tested locally** (GOWORK=off): gofmt, `go vet`, `go vet -tags integration`, the unit suite (a 53-row table against a stand-in console answering like node-tools' mesh_call); the new binary was run against the live console and 13 commands answered. Known: the comment and one row describe `cleanup delete` without `--confirm` as a dry run; the vault refuses instead (harmless; noted on issue 1126). Reviewed-by: review-g2@shanks at 63de1f7e0dd7edec74faef2a677c46656aea100a Pushed-by: lead-47@shanks https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

mesh-tools added 4 commits 2026-11-02 09:48:48 +00:00

nox calls the seats that own each job, not the unassigned controller 5cdf8295f3

The controller nox forwarded every line to is unassigned (issue 1126), so nox
answered nothing but enrol open. Each line now calls the seat verb or module
tool that owns its job through this machine's console (mesh_call); a line no
seat owns says so and names what to use, never failing silently.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

mesh-cli requires the console's endpoint and writes its address a3e9f2cc0f

nox now reaches the mesh through this machine's console, so the module
requires mcp-endpoint and writes the bound address to /etc/mesh-cli/console
rather than trusting a fixed port. No invokes: mesh-cli has no bus account,
and one nothing dials would only be minted.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

nox nodes reads placement with the console's answered-by line after it 9523050a98

The console appends which machine answered after the JSON, so the nodes
table decoded nothing and printed the raw answer; read the first value
and keep the trailer.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

nox cleanup delete confirms with the holder's name, as the vault asks

mesh/delivery merged: source.main moved to novox/mesh-catalog@32c4c52261c4

Details

mesh/check checking 63de1f7e0dd7 on 32c4c52261c4

63de1f7e0d

The vault deletes a retired holder only when confirm repeats its name, so
sending confirm "true" could never delete anything. The stand-in console now
also says which machine answered as a block of its own, as node-tools does.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

mesh-tools commented

2026-11-02 09:48:50 +00:00

Delivery novox/mesh-catalog@63de1f7e0dd7 — merged since 2026-11-02T10:56:35Z

Source — source.main moved to novox/mesh-catalog@32c4c52261. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-02 09:48 (new) → proposed (announced): novox/mesh-catalog#593's head announced
2026-11-02 09:48 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-02 10:56 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@63de1f7e0dd7` — **merged** since 2026-11-02T10:56:35Z **Source** — source.main moved to novox/mesh-catalog@32c4c52261c4. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-02 09:48 (new) → proposed (announced): novox/mesh-catalog#593's head announced - 2026-11-02 09:48 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-02 10:56 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 32c4c52261 into main

2026-11-02 10:56:31 +00:00

mesh-tools deleted branch fix/1126-nox

2026-11-02 10:56:32 +00:00

mesh-tools referenced this pull request

2026-11-02 11:31:17 +00:00

Modules without the controller: vault judges each sensitive caller, nox records its hand acts, provisioner binds ahead of the want (issue 1126 group B) #594

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#593