Actor Runtime

Riot’s actor runtime matters because it gives the system a real execution model rather than only a collection of libraries.

That model centers on:

• isolated processes
• explicit message passing
• supervision-oriented structure

These ideas are useful to users even if they never read runtime internals.

Why users should care

The runtime changes how you think about building systems in Riot.

Instead of starting from shared mutable state and threading concerns outward, the actor model pushes you toward:

• process boundaries
• explicit communication
• clearer fault isolation

That changes the shape of programs in a good way.

What it feels like in practice

At a high level, the promise is:

• independent tasks can become independent processes
• message passing becomes the natural coordination mechanism
• parent/child relationships and supervision become part of system design rather than an afterthought

This is one reason Riot feels more like a runtime ecosystem than just a build tool.

What this page is not

This page is not a deep runtime implementation manual.

It is the user-facing answer to:

• why is the actor model part of Riot’s identity?
• what does that give me as an application author?
• when should I reach for it instead of a simpler synchronous flow?

The contributor-facing internals can live elsewhere. This page should make the runtime approachable.