The launcher: one systemd unit (marius.service) execs the embodiment.
That is the only out-of-band hook — the OS handing control to the embodiment.
The embodiment: marius-embodiment brings up the membrane, runs a node,
delivers nginx via legion://machine/loader, materialises this content over
legion://machine/fs, runs nginx via legion://machine/process, and
watches the content dir — re-materialising any page you edit or insert.
The lifecycle: idle 15 min → the embodiment powers the machine off via
legion://handles/system.shutdown; a scale-to-zero Cloud Run waker starts it on
the next request. Content is durable on the persistent disk and re-materialised on each wake.