This walkthrough is planned but not published yet. The transcript below covers the same material if you would rather read it now.
What @eugo.hpc.distribute actually changes about a function, and what .remote() adds at the call site.
Decorating a function with eugo.hpc.distribute changes how you call it. Instead of running the body immediately and returning a value, a call with .remote() schedules the work somewhere on the cluster and returns a future: a handle to a result that does not exist yet. Your code keeps running. The decision is made once, at the definition site; each call site adds only .remote(), and calling the function directly raises an error that points you to it.