Can I potentially do that several times, or once Materialize has computed up to time B it can’t go back? I was thinking of potentially using Materialize as a proper Leopard-style expanded watch system so I can do my listing queries locally while joining other metadata tables for filtering and sorting. I’m therefore wondering if can do my main streaming from Materialize to keep that index and in parallel do periodic once-off diff checks where I ask Materialize the changes between points A and B (even if those have potentially already been consumed by my primary stream). I don’t know if what I’m saying makes sense 😅