mesh-cli: nox licence is the licences' overview; the controller's leftovers go

The operator typed `nox licence` and got the retired controller's refusal
instead of the licences. `nox licence` and `nox licence list` now call the
licence manager's licences and bindings and print one table of each, every
time local (1126/AC1); `nox licence usage [<licence>]` prints the usage
readings as a table (1126/AC2). `--json` prints the raw answer on every
rendered line, `nox nodes` included: one behaviour for one flag; for the
two calls one object {licences, bindings} (1126/AC3).

In the same change, the operator (2026-11-22 20:41): "why are there still
references to the controller?". Every retired controller line nox answered
with "this was the controller's" (its `instead` lines and the `unowned`
map) is deleted with its text: none has a seat verb of the same job; a
retired line now answers "is not a command" with exit 2, and nothing nox
prints names the controller (1126/AC4). The comments, help and README no
longer name the controller or issue 1126.

Builds: issue 1126 note 151, answers 1-5, and the note after it (acceptance
1126/AC1..AC4, the operator's 20:41 line); one-question-one-tool;
principle 4, a module is steered by its tools.
This commit is contained in:
2026-11-22 20:50:22 +01:00
parent 25e6a46b0a
commit 3ff4df5c6e
8 changed files with 390 additions and 116 deletions
+16 -12
View File
@@ -35,21 +35,24 @@ puts the call on the bus, as every agent session on the machine does. The consol
- **Who judges.** The seat that owns the job: a change of assignments is a proposal the operator approves
(`mesh-module-assigner.propose`), a config value is set with its why (`mesh-config.config`), a silence or a hand act is
recorded as one. Until novox/hq issue 1126 the controller ran these lines and judged the account (ADR 0272); with
the controller unassigned, that judgement went with it.
- **The map.** Every line the controller ran, and the seat verb or tool that does its job now, or none, is
`commands.go`'s table (and hq's `.work/1126/nox-map.md` while issue 1126 runs). A line no seat or module owns says
that it was the controller's, that the controller is unassigned, and what to use instead, and exits 1 having called
nothing. A line nox cannot read says how it is written and exits 2.
recorded as one.
- **The map.** Every line nox takes, and the seat verb or tool that does its job, is `commands.go`'s table. A line
nox does not know, or cannot read, says so and how lines are found or written, and exits 2 having called nothing.
- **Any address.** `nox call <address> [json]` calls any seat verb or tool; `nox search <words>` and
`nox describe <address>` find one and its arguments.
- **What is printed.** The owner's answer as the console gave it (JSON), on standard output with exit 0; an answer the
- **What is printed.** The owner's answer as the console gave it (JSON), or the line's table (`nox nodes`,
`nox licence`, `nox licence usage`; `--json` prints the answer raw), on standard output with exit 0; an answer the
console marks an error (a refusal, nothing serving, no answer within its bound) on standard error with exit 1. A
console that does not answer is said as nothing having been called; no answer in time is said as a call that may
have run.
- **`nox status`** is the delivery view's (`mesh-delivery-view.view_status`). When the view does not answer, nox says
so first, shows the open conditions and the deliveries under their own addresses, and exits 1: they are never
passed off as the status.
- **`nox licence`** (and `nox licence list`) is the operator's overview of the licences in one line
(one-question-one-tool): the licence manager's `licences` as one table (licence, kind, bound nodes, weekly, session
and sonnet usage with their resets, the token's expiry, failures, conditions, whether it is the target), then its
`bindings` (node, licence, since, why), every time local; with `--json` the two answers as one object
`{licences, bindings}`. `nox licence usage [<licence>]` is the manager's `usage` readings as a table.
- **`nox enrol open --key <file>`** runs here and asks nothing of the mesh (ADR 0587 §8).
A process that runs for a verb (it carries `MESH_VERB`) is refused before anything is called: a verb is never the
@@ -57,15 +60,16 @@ operator.
## What it does not do yet
- **No formatting beyond `nox nodes`.** Answers are the owners' JSON.
- **Lines with no owner.** Accepting a secret from a person, making or setting the operator key, opening a sealed
secret locally, registering a module from another repository and forgetting a module have no seat verb yet; nox
names what to use meanwhile.
- **No formatting beyond `nox nodes` and the licence lines.** Answers are the owners' JSON.
- **No line without a seat verb.** Accepting a secret from a person, making or setting the operator key, opening a
sealed secret locally, registering a module from another repository and forgetting a module have no seat verb yet,
so nox has no line for them.
## Tests
`go test ./...`: every owned line calls its owner's address with the arguments it reads, against a stand-in console
answering MCP `tools/call` as node-tools does; a line with no owner or not read calls nothing and says why; an error
answering MCP `tools/call` as node-tools does; a line not known or not read calls nothing and says why; the licence
lines print their tables from the manager's answers; an error
answer, a silent console and a verb's process are said; the status's fallback is labelled and exits 1; the console's
address is found; `enrol open` opens a sealed token locally; the module places the program and the console's address
and nothing else.