going back to a previous conversation: > if you choose to not use ZedTokens, your staleness risk is minimal but still real: if you're okay with staleness for at most a few 10s of seconds (its usually configured much lower), then you can simply not use ZedTokens at all for the "configured much lower" part, does that mean there's some part of the configuration that allows you to dictate how often the cache is invalidated? I ask because my team asked how

minimize_latency

works, and I realized that I'm not actually sure when and how SpiceDB would do the work of going to the datastore and recomputing a particular subproblem if you've got

minimize_latency

selected. (it's obvious to me for both

at_least_as_fresh

and

fully_consistent

- it's looking at the zedtoken and discarding any results that are less than the specified revision)