Just read something similar with Urbit: https://urbit.org/docs/introduction/technical-overview/ https://urbit.org/docs/introduction/technical-overview/ Taking

Just read something similar with Urbit: https://urbit.org/docs/introduction/technical-overview/ https://urbit.org/docs/introduction/technical-overview/ Taking that concept to an operating system essentially. > Your urbit is a deterministic computer in the sense that its state is a pure function of its event history. Every event in this history is a transaction; your urbit's state is effectively an ACID database. > Because each urbit is deterministic we can describe its role appropriately in purely functional terms: it maps an input event and the old urbit state to a list of output actions and the subsequent state. This is the Urbit transition function.