Comparison with Urbit

[jpt4]

Is the author familiar with Urbit [0], and whether it would qualify as an eidetic system? Urbit executes within a virtual machine that runs a purely functional distributed system OS called Arvo. Arvo is a functional, single-threaded event based architecture that models all process execution as responses to message packets of data and/or data-encoded code from the network (of which its own instance is a node). The sequential receipt of these packets produces an event log which allows Arvo to compute its current state, and deterministically replay all previous states, as a pure function of its history. This allows for e.g. debugging the cause of a spurious infinite loop.

Urbit is a program that runs in user space, which simplifies certain implementation difficulties faced when developing for native kernels, but this aspect of the design goals seem the same: to track the lineage of a computer's state, in a queryable way. Is this accurate? Are there features of eidetic computing that fundamentally distinguish omniplay and Urbit?

[0] urbit.org, github.com/urbit/urbit