Seems like you could dispatch an event at regular intervals, then control the flow somehow so it's only live when that event runs. Then you'd have that kind of debouncey behavior where the calculation only runs on that particular event.

A flow can have an input from the same app-db path as its output. Maybe that comes in handy too. A flow could output a value that causes it to become dead. Then, your event could make it live again, perhaps by registering it. Worth playing around with, maybe a nice pattern will emerge.

Your :output function could return something like this: {:value "your calculation result" :dirty? false}. Then other events could set :dirty? true at the right time. And your :live? function could basically be a getter for that :dirty value.