Interesting.

Your use of the word "Reactor" at first confused me since there is a "Reactor Pattern" for event handling (https://en.wikipedia.org/wiki/Reactor_pattern) which is not what you mean.

How does your concurrency model differ from that of Erlang (the poster child for distributed concurrency)? Do you have a paper detailing your model and comparing with other languages?

I recently read Roman Obermaisser's excellent book "Event-Triggered and Time-Triggered Control Paradigms" which seems applicable to your architecture. At the bottom most level you have a global communication network based on a synchronized global clock and "Time-Triggered"(TT) semantics which is deterministic. A "Event-Triggered"(ET) communication channel is then overlaid on top of it which is non-deterministic. That way the system provides both hard real-time (i.e. TT) and soft real-time (i.e. ET) semantics.