Politely :) I would like to know your experience level with distributed F/T systems. I ask because they are not just throwing around buzz words: they are being quite precise with defining their platform. I skimmed that readme and it was quite clear, and in fact 'Bastion Executor' bit aroused a bit of Rust envy.

Some follow up questions for me would be around the messaging guarantee (AMO) and what sort of effort is required to, say, implement OTP semantics in Bastion.

Here is Erlang OTP's doc with code snippets for your comparative reference:

https://erlang.org/doc/design_principles/des_princ.html

Probably clear I don’t have a lot of experience! :)

But maybe I should? Maybe that example would help? :)

You definitely should learn - it's a lovely domain for geeking out -- but you first need to acquaint yourself with the technical domain. I honestly don't see how an example would get you from 0 to nodes up and running with understanding.

Here are two good starting points (since Bastion is the same type of platform): https://learnyousomeerlang.com/what-is-otp

https://dockyard.com/blog/2018/07/18/all-for-reliability-ref...

That first link has what you want: examples. But note how many pieces are involved and that it is not a 5 minute read :)

Top level, a project like this needs to communicate to the intended audiance -- here, people who are building F/T distributed actor systems -- what the project brings to the table, and imo they did a good job in that regard.

Good points. In the mean time you can read what Akka and Erlang are. They are both actor based systems. From a quick glance that is what Bastion is as well.