Can you elaborate on this? Even if the goal is learning, wouldn’t you want to learn good patterns around state persistence rather than bad ones? I suspect it is technically possible to achieve what you’re trying to do but I don’t think it would be a good solution for any real use case, because…
when the node that is parent of the said process dies
…AFAIK there are no guarantees around this that would allow for safe persistence of data.
Assuming you already know all that and want an answer anyway, I would guess that you would want to duplicate each state change across nodes (maybe using something like Phoenix.PubSub) rather than try to “hand it off” just in time.
