The trust bed raises a mesh, and places the bus's users as genesis must #53

2026-09-29T15:37:55Z

jschoubben commented

2026-09-29 15:37:55 +00:00

The bed now does what raising a first node actually takes. The private network, because the authority certifies itself for the address it holds there and a machine with no overlay has not got one. And the composed user list placed beside the bus at the two moments an account comes into existence — when the token is issued, and when the machine enrols — because neither can arrive in a declaration: a machine that has not enrolled gets none.

MESH_LAB_KEEP leaves the machine standing, which is where every answer in this sequence came from: the host's log, the bus's log, and the accounts file it was actually given.

No module issue for the authority — that delivers a bus account and the authority declares none.

The bed still fails, at the machine being enrolled twice from one attempt. Everything before that now works from bare: foundation, certificate, bus, control plane, token, enrolment.

novox/hq [issue 146](https://git.novox.be/novox/hq). The bed now does what raising a first node actually takes. The private network, because the authority certifies itself for the address it holds there and a machine with no overlay has not got one. And the composed user list placed beside the bus at the two moments an account comes into existence — when the token is issued, and when the machine enrols — because neither can arrive in a declaration: a machine that has not enrolled gets none. `MESH_LAB_KEEP` leaves the machine standing, which is where every answer in this sequence came from: the host's log, the bus's log, and the accounts file it was actually given. No `module issue` for the authority — that delivers a bus account and the authority declares none. **The bed still fails**, at the machine being enrolled twice from one attempt. Everything before that now works from bare: foundation, certificate, bus, control plane, token, enrolment.

jschoubben added 1 commit 2026-09-29 15:37:55 +00:00

The trust bed raises a mesh, and places the bus's users as genesis must f2d6ab3bf9

novox/hq 04-ISSUES/146. The bed now does what raising a first node actually
takes: the private network so the authority can certify the address it holds,
and the composed user list placed beside the bus at the two moments an account
comes into existence — when the token is issued, and when the machine enrols.
Neither can arrive in a declaration, because a machine that has not enrolled
gets none.

MESH_LAB_KEEP leaves the machine standing, which is where every answer in this
sequence came from. No 'module issue' for the authority: that delivers a bus
account and it declares none.

The bed still fails, at the machine being enrolled twice from one attempt.

jschoubben added 1 commit 2026-09-29 15:45:11 +00:00

A bed says what it actually needs to be pointed at a734d427c0

The instructions in every bed named the bundle that raises the predecessor's
broker, so a first attempt ends in a control plane crash-looping on a missing
MESH_BUS_NATS — which reads like a broken lab. They name the bundle that works
now, and the README says the host binary needs SYSTEM=arch, because one built
without it refuses everything with an empty system name.

And the three habits that each cost a run before they were adopted:
MESH_LAB_KEEP to leave the machine standing, MESH_LAB_WARM while iterating,
and rebuilding all three repositories the bed places rather than the one that
changed.

mesh-admin merged commit a4f6bb8ce0 into main

2026-10-01 11:18:12 +00:00

mesh-admin deleted branch feat/the-trust-bed-raises-a-mesh

2026-10-01 11:18:13 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#53