Suggested roadmap: start with the runtime

To validate that the model works in practice, the recommended order:

1. Process micro-kernel: create a process with its own stack and heap.
2. Basic scheduler: a loop alternating between two processes (start with work-stealing).
3. IPC with @transfer: validate that the source’s memory is invalidated after the transfer, the passing that moves, distinct from the copy (which preserves the source).
4. Death signal: the parent process receives DOWN when the child dies, expressed as error-as-value in the catch.
5. spawn-block coordinator: validate that the coordinator kills siblings correctly in the one_for_all and rest_for_one strategies.

The compiler comes later; the runtime is the foundation. If the model of isolated processes does not perform as expected, it is better to find that out early.