hq ADR 0277 (hq PR #278). The operator's first use: mounts' sources on shanks (tracker issue 379).
What it does. Anyone the bus admits may PROPOSE a settings layer, the trusted keys included (issue 339's refusal through settings stands and now names the proposal):
settings {module, node, values, propose: true [, replace]} / {module, node, clear: true, propose: true} → settings propose <module> <values | --clear> [--node] [--replace]. The proposal is judged as settings set judges (nothing is asked for a layer the mesh would refuse; a removal without replace is refused, ADR 0217), kept in the controller's own asked bucket (which the controller alone writes), and asked of the operator under the controller's name at the level approve (Approve / Decline, both binding an act digest): module, machine, every key with its exact new value — in its shape (recalbox=‹address›@‹path›) where a path or an address may not leave the mesh (the router's content rule) — the was of a changed key, the removed keys, the layer's fingerprint, and where the whole is read (settings {proposal: <id>} / settings proposals <id>).
The serving controller sets the layer on the warrant alone (asker.Decided → decideProposal → setLayerIn): once per ask by compare-and-set (a replay changes nothing); only on a warrant whose ask digest is the kept ask's; only when the record's values still digest to the digest the option bound, and the layer is still the one the operator was shown it against; with the terminal's own judgement and history. Who approved it is kept beside the layer (migration 0090 set_by), and settings show says "approved by the operator, as telegram identity …, via telegram (…) at … (ask …, proposed by …)"; a layer set at the terminal / through a verb says so too. The warrant is recorded in the hand-act log under warrant (a person's decision).
Decline, expiry, cancel, replacement, the router's refusal: nothing set, recorded as ended. Fail closed: no router, no grant, publish failed, words the content rule refuses → refused at once naming the terminal's line; the verb waits up to 8 s for the router's refusal and says it. Bounds: a fourth open ask refused; the same change twice refused; proposals count toward the controller's three open asks.
settings proposals [<id>] lists / shows one whole (also a read of the generic command verb). The push afterwards stays a separate act.
Not in this PR: a seat event for the set (the installer's first user list in mesh-host names every controller event; the hand-act log, the layer's provenance and the router's edit of the ask carry it) and the secret-ask verb (second PR, stacked on this one).
Reviewer's checklist: no path sets a trusted setting without a proven warrant (refuseTerminalSettingsThroughAVerb unchanged; setLayer is reached only from asker.Decided); the warrant binds the exact values (decideProposal: values digest and before-digest recomputed from the record against the act the option bound; TestAWarrantSetsOnlyTheExactValuesTheOperatorWasShown); replay refused (TestTheLayerIsSetOnceOnTheOperatorsApproval); fails closed (TestAProposalFailsClosedWhenNothingCanCarryIt).
Tests: cmd/mesh-controller/proposals_test.go (13 tests, the store-backed ones against the throwaway postgres). merge-check.sh run locally against a throwaway store.
hq ADR 0277 (hq PR #278). The operator's first use: mounts' `sources` on shanks (tracker issue 379).
**What it does.** Anyone the bus admits may PROPOSE a settings layer, the trusted keys included (issue 339's refusal through `settings` stands and now names the proposal):
- `settings {module, node, values, propose: true [, replace]}` / `{module, node, clear: true, propose: true}` → `settings propose <module> <values | --clear> [--node] [--replace]`. The proposal is judged as `settings set` judges (nothing is asked for a layer the mesh would refuse; a removal without replace is refused, ADR 0217), kept in the controller's own `asked` bucket (which the controller alone writes), and asked of the operator under the controller's name at the level **approve** (Approve / Decline, both binding an act digest): module, machine, every key with its exact new value — in its shape (`recalbox=‹address›@‹path›`) where a path or an address may not leave the mesh (the router's content rule) — the `was` of a changed key, the removed keys, the layer's fingerprint, and where the whole is read (`settings {proposal: <id>}` / `settings proposals <id>`).
- The **serving controller** sets the layer on the warrant alone (asker.Decided → decideProposal → setLayerIn): once per ask by compare-and-set (a replay changes nothing); only on a warrant whose ask digest is the kept ask's; only when the record's values still digest to the digest the option bound, and the layer is still the one the operator was shown it against; with the terminal's own judgement and history. Who approved it is kept beside the layer (migration 0090 `set_by`), and `settings show` says "approved by the operator, as telegram identity …, via telegram (…) at … (ask …, proposed by …)"; a layer set at the terminal / through a verb says so too. The warrant is recorded in the hand-act log under `warrant` (a person's decision).
- Decline, expiry, cancel, replacement, the router's refusal: nothing set, recorded as ended. Fail closed: no router, no grant, publish failed, words the content rule refuses → refused at once naming the terminal's line; the verb waits up to 8 s for the router's refusal and says it. Bounds: a fourth open ask refused; the same change twice refused; proposals count toward the controller's three open asks.
- `settings proposals [<id>]` lists / shows one whole (also a read of the generic `command` verb). The push afterwards stays a separate act.
**Not in this PR**: a seat event for the set (the installer's first user list in mesh-host names every controller event; the hand-act log, the layer's provenance and the router's edit of the ask carry it) and the `secret-ask` verb (second PR, stacked on this one).
**Reviewer's checklist**: no path sets a trusted setting without a proven warrant (`refuseTerminalSettingsThroughAVerb` unchanged; `setLayer` is reached only from `asker.Decided`); the warrant binds the exact values (`decideProposal`: values digest and before-digest recomputed from the record against the act the option bound; `TestAWarrantSetsOnlyTheExactValuesTheOperatorWasShown`); replay refused (`TestTheLayerIsSetOnceOnTheOperatorsApproval`); fails closed (`TestAProposalFailsClosedWhenNothingCanCarryIt`).
Tests: `cmd/mesh-controller/proposals_test.go` (13 tests, the store-backed ones against the throwaway postgres). `merge-check.sh` run locally against a throwaway store.
Deliverynovox/mesh-controller@cc11de2513ae — delivered since 2026-10-10T13:10:32Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 3m37s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m42s
build-agent on the rest running it: sent
Transitions
2026-10-10 12:43 (new) → proposed (announced): novox/mesh-controller#199's head announced
2026-10-10 12:49 proposed → checked (checked): the verdict names this commit
2026-10-10 12:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 13:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-10 13:00 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-10 13:10 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@cc11de2513ae` — **delivered** since 2026-10-10T13:10:32Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m37s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m42s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-10 12:43 (new) → proposed (announced): novox/mesh-controller#199's head announced
- 2026-10-10 12:49 proposed → checked (checked): the verdict names this commit
- 2026-10-10 12:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 13:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-10 13:00 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-10 13:10 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 → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
Issue 339 made every trusted setting the controller's terminal's alone, so an agent could only hand the
operator a line to type at the control node. Now anyone the bus admits may PROPOSE a layer: settings
propose keeps the proposal in the controller's own asks (the asked bucket, which the controller alone
writes), judged as settings set judges, and asks the operator on the operator channel at the level
approve with every key, its exact new value (in its shape where a path or an address may not leave the
mesh), the was of a changed key, the removed keys and the layer's fingerprint. The serving controller
sets the layer on the warrant alone: once, for the ask it holds, only when the record's values still
digest to what the option bound and the layer is still the one shown, with the terminal's judgement and
history, and keeps who approved it beside the layer, which settings says back (migration 0090). Decline,
expiry, a cancel, a replacement or the router's refusal discard it; nothing is asked when no router, no
grant or no channel can carry it. settings proposals lists them. The push afterwards is a separate act.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: cmd/mesh-controller/proposals_test.go
Run by the build seat on novox as build-1791635667958656739 (builds --log build-1791635667958656739).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 55 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-10T12:28:18Z 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-10T12:28:18Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- 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 273.949s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.044s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/route-proxy 1.182s
ok github.com/novox/mesh-controller/internal/artifacts 1.067s
ok github.com/novox/mesh-controller/internal/broker 3.031s
ok github.com/novox/mesh-controller/internal/builder 4.128s
ok github.com/novox/mesh-controller/internal/catalogue 5.811s
ok github.com/novox/mesh-controller/internal/conditions 2.644s
ok github.com/novox/mesh-controller/internal/envfile 1.042s
ok github.com/novox/mesh-controller/internal/facts 1.039s
ok github.com/novox/mesh-controller/internal/identity 5.373s
ok github.com/novox/mesh-controller/internal/inventory 102.358s
ok github.com/novox/mesh-controller/internal/lease 17.719s
ok github.com/novox/mesh-controller/internal/licences 4.916s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s
ok github.com/novox/mesh-controller/internal/link 58.669s
ok github.com/novox/mesh-controller/internal/lint 2.375s
ok github.com/novox/mesh-controller/internal/outward 1.040s
ok github.com/novox/mesh-controller/internal/overlay 1.024s
ok github.com/novox/mesh-controller/internal/secrets 1.542s
ok github.com/novox/mesh-controller/internal/store 3.422s
ok github.com/novox/mesh-controller/internal/testbus 1.202s
ok github.com/novox/mesh-controller/internal/token 1.018s
**Merge check** at `e2a51f05`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: cmd/mesh-controller/proposals_test.go
Run by the build seat on novox as `build-1791635667958656739` (`builds --log build-1791635667958656739`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 55 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-10T12:28:18Z 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-10T12:28:18Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- 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 273.949s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.044s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/route-proxy 1.182s
ok github.com/novox/mesh-controller/internal/artifacts 1.067s
ok github.com/novox/mesh-controller/internal/broker 3.031s
ok github.com/novox/mesh-controller/internal/builder 4.128s
ok github.com/novox/mesh-controller/internal/catalogue 5.811s
ok github.com/novox/mesh-controller/internal/conditions 2.644s
ok github.com/novox/mesh-controller/internal/envfile 1.042s
ok github.com/novox/mesh-controller/internal/facts 1.039s
ok github.com/novox/mesh-controller/internal/identity 5.373s
ok github.com/novox/mesh-controller/internal/inventory 102.358s
ok github.com/novox/mesh-controller/internal/lease 17.719s
ok github.com/novox/mesh-controller/internal/licences 4.916s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s
ok github.com/novox/mesh-controller/internal/link 58.669s
ok github.com/novox/mesh-controller/internal/lint 2.375s
ok github.com/novox/mesh-controller/internal/outward 1.040s
ok github.com/novox/mesh-controller/internal/overlay 1.024s
ok github.com/novox/mesh-controller/internal/secrets 1.542s
ok github.com/novox/mesh-controller/internal/store 3.422s
ok github.com/novox/mesh-controller/internal/testbus 1.202s
ok github.com/novox/mesh-controller/internal/token 1.018s
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: cmd/mesh-controller/proposals_test.go
Run by the build seat on ace as build-1791636187789204006 (builds --log build-1791636187789204006).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 55 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-10T12:37:18Z 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-10T12:37:18Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/proposals_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.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 199.837s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/route-proxy 1.111s
ok github.com/novox/mesh-controller/internal/artifacts 1.099s
ok github.com/novox/mesh-controller/internal/broker 2.666s
ok github.com/novox/mesh-controller/internal/builder 2.536s
ok github.com/novox/mesh-controller/internal/catalogue 4.572s
ok github.com/novox/mesh-controller/internal/conditions 2.482s
ok github.com/novox/mesh-controller/internal/envfile 1.065s
ok github.com/novox/mesh-controller/internal/facts 1.092s
ok github.com/novox/mesh-controller/internal/identity 4.193s
ok github.com/novox/mesh-controller/internal/inventory 75.126s
ok github.com/novox/mesh-controller/internal/lease 17.727s
ok github.com/novox/mesh-controller/internal/licences 3.829s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.086s
ok github.com/novox/mesh-controller/internal/link 51.371s
ok github.com/novox/mesh-controller/internal/lint 2.085s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.099s
ok github.com/novox/mesh-controller/internal/secrets 1.434s
ok github.com/novox/mesh-controller/internal/store 3.338s
ok github.com/novox/mesh-controller/internal/testbus 1.260s
ok github.com/novox/mesh-controller/internal/token 1.018s
**Merge check** at `cc11de25`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: cmd/mesh-controller/proposals_test.go
Run by the build seat on ace as `build-1791636187789204006` (`builds --log build-1791636187789204006`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 55 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-10T12:37:18Z 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-10T12:37:18Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/proposals_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.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 199.837s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/route-proxy 1.111s
ok github.com/novox/mesh-controller/internal/artifacts 1.099s
ok github.com/novox/mesh-controller/internal/broker 2.666s
ok github.com/novox/mesh-controller/internal/builder 2.536s
ok github.com/novox/mesh-controller/internal/catalogue 4.572s
ok github.com/novox/mesh-controller/internal/conditions 2.482s
ok github.com/novox/mesh-controller/internal/envfile 1.065s
ok github.com/novox/mesh-controller/internal/facts 1.092s
ok github.com/novox/mesh-controller/internal/identity 4.193s
ok github.com/novox/mesh-controller/internal/inventory 75.126s
ok github.com/novox/mesh-controller/internal/lease 17.727s
ok github.com/novox/mesh-controller/internal/licences 3.829s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.086s
ok github.com/novox/mesh-controller/internal/link 51.371s
ok github.com/novox/mesh-controller/internal/lint 2.085s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.099s
ok github.com/novox/mesh-controller/internal/secrets 1.434s
ok github.com/novox/mesh-controller/internal/store 3.338s
ok github.com/novox/mesh-controller/internal/testbus 1.260s
ok github.com/novox/mesh-controller/internal/token 1.018s
```
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.
hq ADR 0277 (hq PR #278). The operator's first use: mounts'
sourceson shanks (tracker issue 379).What it does. Anyone the bus admits may PROPOSE a settings layer, the trusted keys included (issue 339's refusal through
settingsstands and now names the proposal):settings {module, node, values, propose: true [, replace]}/{module, node, clear: true, propose: true}→settings propose <module> <values | --clear> [--node] [--replace]. The proposal is judged assettings setjudges (nothing is asked for a layer the mesh would refuse; a removal without replace is refused, ADR 0217), kept in the controller's ownaskedbucket (which the controller alone writes), and asked of the operator under the controller's name at the level approve (Approve / Decline, both binding an act digest): module, machine, every key with its exact new value — in its shape (recalbox=‹address›@‹path›) where a path or an address may not leave the mesh (the router's content rule) — thewasof a changed key, the removed keys, the layer's fingerprint, and where the whole is read (settings {proposal: <id>}/settings proposals <id>).set_by), andsettings showsays "approved by the operator, as telegram identity …, via telegram (…) at … (ask …, proposed by …)"; a layer set at the terminal / through a verb says so too. The warrant is recorded in the hand-act log underwarrant(a person's decision).settings proposals [<id>]lists / shows one whole (also a read of the genericcommandverb). The push afterwards stays a separate act.Not in this PR: a seat event for the set (the installer's first user list in mesh-host names every controller event; the hand-act log, the layer's provenance and the router's edit of the ask carry it) and the
secret-askverb (second PR, stacked on this one).Reviewer's checklist: no path sets a trusted setting without a proven warrant (
refuseTerminalSettingsThroughAVerbunchanged;setLayeris reached only fromasker.Decided); the warrant binds the exact values (decideProposal: values digest and before-digest recomputed from the record against the act the option bound;TestAWarrantSetsOnlyTheExactValuesTheOperatorWasShown); replay refused (TestTheLayerIsSetOnceOnTheOperatorsApproval); fails closed (TestAProposalFailsClosedWhenNothingCanCarryIt).Tests:
cmd/mesh-controller/proposals_test.go(13 tests, the store-backed ones against the throwaway postgres).merge-check.shrun locally against a throwaway store.Delivery
novox/mesh-controller@cc11de2513ae— delivered since 2026-10-10T13:10:32ZDelivery plan — builds build-agent, mesh-controller → 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.e2a51f05bbtocc11de2513Merge check at
e2a51f05mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791635667958656739(builds --log build-1791635667958656739).Merge check at
cc11de25mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791636187789204006(builds --log build-1791636187789204006).