Well, so I'd like to be able to do the equivalent of what is done with can.computes, where if a value cross-bound using an attr selector/compute is used within the getter, and then changes, the defined property would re-compute and emit a change event. In essence, something that takes the signature of a manual can.compute(get/set/on/off) as well as serialize. That way, changes in other properties, such as current page, or query term, would result in recomputation.
It would be even more swell if this could be done in a way in which there was an asynchronous setter, such that a route change would result in the respective findAll/findOne, and asynchronously set the attribute as the loaded document before emitting change.