Consuming changes via the

Watch

API, if I receive a first change and recompute some expanded relations using a

LookupResources

call that gives me a ZedToken that the LR is evaluated at. If I then receive another change in the

Watch

API that will affect the same user, and that change's ZedToken is before the ZedToken I got from my LR call, I want to bypass having to re-call LR because I know that the recomputation I did already included those changes