Not sure if it's inspiring or not, but it's my labor of love. I kept it going after grad school. I work on it a little bit every day, and slowly but surely it's becoming what I originally envisioned as my ultimate parallel programming system.
imho you could stand to distinguish it more clearly from the Raft consensus protocol
Unfortunately anything published at uni's like Stanford has immediate potential for faster dissemination. I'm either going to have to wait out the extinction of the Raft consensus protocol (or at least for something better to come along) or to get a better name. Stream processing systems are also synonymous with "Data-flow." They all have a history of punny names (See StreamC, StreamIt, Brook, WaveScript, FloodGate, RapidMind, even Cuda is a play on barracuda which has it's origins in stream processing from the academic Brook project). So if I were to get a better name, I'd have to find something equally punny (and likely create redirects from about 11/12 academic pubs, journal papers, etc.). If you have any suggestions I'm definitely open :).