Is there a way to do the opposite of the

at_least_as_fresh

(

no_fresher_than

?) consistency? Use case: trying to determine the state of the system before a given change coming from the

Watch

API, I could always store the previous ZedToken and do a call with

at_exact_snapshot

with that previous token but it's not ideal, so I was wondering if there was a way to do the opposite of

at_least_as_fresh

where I don't care about the exact point in time as long as it's no fresher than the provided ZedToken