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

Let a block show a value its module keeps on the bus, and grant the bar the read (hq ADR 0260) #149

Merged
mesh-admin merged 1 commits from feat/the-bar-takes-blocks into main 2026-10-08 13:46:15 +00:00
Conversation 2 Commits 1 Files Changed 6
+192 -9
mesh-admin commented 2026-10-08 13:33:06 +00:00
Contributor
Copy Link
Copy Source

Part of the delivery group feat/the-bar-takes-blocks, with mesh-catalog #127 and hq #212 (ADR 0260). Modules talk over the bus; ADR 0255 had the bar print the power module's file.

  • shows: state in the node-bar block shape: options state (<module>.<name>) and optional key, the machine's name when absent. The holder's template now also sees machine.
  • A module offers its own state only: a block naming another module's state, or one the contributor does not keep, is refused at registration (ownStateProblems).
  • The holder is granted the read (ReadsGranted, wired into BusRecords per machine): every state the modules on the holder's machine offer in pieces of a kind its seat receives as data. The bar's manifest names no module; a bar without the power module beside it reads nothing of it.

Tests: TestAStateBlockIsRenderedForThisMachineAndTheHolderIsGrantedToReadIt, TestAModuleOffersItsOwnStateOnly (catalogue), TestABarIsGrantedTheStateItsMachinesModulesOfferIt (inventory, against a real store). merge-check.sh passes locally.

Merge order: this, then mesh-catalog #127 (rechecked once this controller is live). Do not merge without the operator's approval.

Part of the delivery group `feat/the-bar-takes-blocks`, with mesh-catalog #127 and hq #212 (ADR 0260). Modules talk over the bus; ADR 0255 had the bar print the power module's file. - **`shows: state`** in the node-bar block shape: options `state` (`<module>.<name>`) and optional `key`, the machine's name when absent. The holder's template now also sees `machine`. - **A module offers its own state only**: a block naming another module's state, or one the contributor does not keep, is refused at registration (`ownStateProblems`). - **The holder is granted the read** (`ReadsGranted`, wired into `BusRecords` per machine): every state the modules on the holder's machine offer in pieces of a kind its seat receives as data. The bar's manifest names no module; a bar without the power module beside it reads nothing of it. Tests: `TestAStateBlockIsRenderedForThisMachineAndTheHolderIsGrantedToReadIt`, `TestAModuleOffersItsOwnStateOnly` (catalogue), `TestABarIsGrantedTheStateItsMachinesModulesOfferIt` (inventory, against a real store). `merge-check.sh` passes locally. Merge order: this, then mesh-catalog #127 (rechecked once this controller is live). Do not merge without the operator's approval.
mesh-admin added 1 commit 2026-10-08 13:33:07 +00:00
Let a block show a value its module keeps on the bus, and grant the bar the read (hq ADR 0260)
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 delivered
Details
d9588b4f13 
Modules talk over the bus, and the power draw reached the bar through a file. A block
may now show state its contributor keeps, the contributor only its own; the holder on
the same machine is granted the read without naming the module, and the template sees
which machine it renders for.
mesh-admin commented 2026-10-08 13:33:19 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-controller@d9588b4f1360 — delivered since 2026-10-08T14:00:52Z

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 3m20s
  • build-agent on the rest running it: sent
  • route-proxy on ace: passed — healthy 3 times over 3m31s
  • route-proxy on the rest running it: sent

Transitions

  • 2026-10-08 13:33 (new) → proposed (announced): novox/mesh-controller#149's head announced
  • 2026-10-08 13:37 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 13:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 13:46 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:46 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 14:00 delivering → delivered (done): its walk is done: 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@d9588b4f1360` — **delivered** since 2026-10-08T14:00:52Z **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 3m20s - build-agent on the rest running it: sent - route-proxy on ace: passed — healthy 3 times over 3m31s - route-proxy on the rest running it: sent **Transitions** - 2026-10-08 13:33 (new) → proposed (announced): novox/mesh-controller#149's head announced - 2026-10-08 13:37 proposed → checked (checked): the verdict names this commit - 2026-10-08 13:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 13:46 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:46 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 14:00 delivering → delivered (done): its walk is done: 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-admin commented 2026-10-08 13:38:00 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at d9588b4f

  • 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-1791466397164984601 (builds --log build-1791466397164984601).

--- 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-08T13:32:02Z 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-08T13:32:02Z

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.033s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	164.760s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.047s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.053s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.044s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.209s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.079s
ok  	github.com/novox/mesh-controller/internal/broker	2.635s
ok  	github.com/novox/mesh-controller/internal/builder	1.819s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.834s
ok  	github.com/novox/mesh-controller/internal/conditions	2.226s
ok  	github.com/novox/mesh-controller/internal/envfile	1.042s
ok  	github.com/novox/mesh-controller/internal/facts	1.058s
ok  	github.com/novox/mesh-controller/internal/identity	4.768s
ok  	github.com/novox/mesh-controller/internal/inventory	79.642s
ok  	github.com/novox/mesh-controller/internal/lease	17.701s
ok  	github.com/novox/mesh-controller/internal/licences	4.305s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.065s
ok  	github.com/novox/mesh-controller/internal/link	46.254s
ok  	github.com/novox/mesh-controller/internal/lint	2.066s
ok  	github.com/novox/mesh-controller/internal/outward	1.079s
ok  	github.com/novox/mesh-controller/internal/overlay	1.065s
ok  	github.com/novox/mesh-controller/internal/secrets	1.536s
ok  	github.com/novox/mesh-controller/internal/store	3.452s
ok  	github.com/novox/mesh-controller/internal/testbus	1.233s
ok  	github.com/novox/mesh-controller/internal/token	1.014s
**Merge check** at `d9588b4f` - `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-1791466397164984601` (`builds --log build-1791466397164984601`). ``` --- 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-08T13:32:02Z 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-08T13:32:02Z 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.033s ok github.com/novox/mesh-controller/cmd/mesh-controller 164.760s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.047s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.053s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.044s ok github.com/novox/mesh-controller/examples/route-proxy 1.209s ok github.com/novox/mesh-controller/internal/artifacts 1.079s ok github.com/novox/mesh-controller/internal/broker 2.635s ok github.com/novox/mesh-controller/internal/builder 1.819s ok github.com/novox/mesh-controller/internal/catalogue 4.834s ok github.com/novox/mesh-controller/internal/conditions 2.226s ok github.com/novox/mesh-controller/internal/envfile 1.042s ok github.com/novox/mesh-controller/internal/facts 1.058s ok github.com/novox/mesh-controller/internal/identity 4.768s ok github.com/novox/mesh-controller/internal/inventory 79.642s ok github.com/novox/mesh-controller/internal/lease 17.701s ok github.com/novox/mesh-controller/internal/licences 4.305s ok github.com/novox/mesh-controller/internal/licences/adapters 1.065s ok github.com/novox/mesh-controller/internal/link 46.254s ok github.com/novox/mesh-controller/internal/lint 2.066s ok github.com/novox/mesh-controller/internal/outward 1.079s ok github.com/novox/mesh-controller/internal/overlay 1.065s ok github.com/novox/mesh-controller/internal/secrets 1.536s ok github.com/novox/mesh-controller/internal/store 3.452s ok github.com/novox/mesh-controller/internal/testbus 1.233s ok github.com/novox/mesh-controller/internal/token 1.014s ```
mesh-admin merged commit 41d6019fa0 into main 2026-10-08 13:46:15 +00:00
mesh-admin deleted branch feat/the-bar-takes-blocks 2026-10-08 13:46:15 +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
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#149