Attach the node to a private network (a grant; body names the network)

Attach a node to a private network in your workspace - a grant, like expose_port: mutable, audited, and live (a running member converges in place within seconds; no restart). The node gets stable private addresses (the response's v4/v6), keeps them for its whole life across stop/wake/recreate/repair, and can then reach - and be reached by - every other member ON ALL PORTS: one trust zone, so joining a network is trusting its members. One network per node (v1); detach_network first to move. Attachment is placement-independent: queued and stopped nodes attach fine - a stopped member keeps its addresses and simply drops traffic (nothing wakes on mesh traffic; a wake is always an explicit command). East-west only: the mesh never carries internet transit, and public reachability stays expose_port's job. The response's data_plane says whether the mesh interface exists on the node right now. up means gmn0 is in the container. converging means the interface installs on the host's next heartbeat, normally within a few seconds; if it still reads converging after about a minute, file a ticket with the node name. not_placed means the node is stopped or queued and joins at its next wake. unavailable means the host that runs the node has no mesh support; the membership and the addresses hold, and the interface appears when the host gains mesh support or the node runs on a host that has it. Nothing on your side changes that. get_node, list_nodes, list_networks, and /v1/network from inside a member carry the same field.