The network map resolves each machine with the seat holders on record #99

2026-09-27T22:55:58Z

jschoubben commented

2026-09-27 22:55:58 +00:00

Without them, a machine running the next holder of a seat beside the current one resolves as two holders, is refused, and drops out of the map — and with it the address every other machine composes for what it offers. Found live: the control node vanished from the private network the moment the new bus was assigned beside the old one, and nothing on any machine could be composed (${machine:at} empty on the control node; the artifact store "not on the private network" for the others). The only Resolve call that lacked the record.

Without them, a machine running the next holder of a seat beside the current one resolves as two holders, is refused, and drops out of the map — and with it the address every other machine composes for what it offers. Found live: the control node vanished from the private network the moment the new bus was assigned beside the old one, and nothing on any machine could be composed (`${machine:at}` empty on the control node; the artifact store "not on the private network" for the others). The only `Resolve` call that lacked the record.

jschoubben added 1 commit 2026-09-27 22:55:58 +00:00

The network map resolves each machine with the seat holders on record 9b715524a2

Without them, a machine running the next holder of a seat beside the current one
resolves as two holders, is refused, and drops out of the map — and with it the
address every other machine composes for what it offers. Found live: the control
node vanished from the private network the moment the new bus was assigned beside
the old one, and nothing on any machine could be composed.

jschoubben merged commit 83671fae5f into main

2026-09-27 22:56:56 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#99