Okay, I'm going to claim that this is the right way to go: what ivy invalidates and truly operates over is a subgraph, BUT it has the ability to throw away a lot of the structure of that subgraph (it already does that in fact, its FingerprintStrategy was motivated by the need to not worry about JvmTarget hashes in thesubgraph). Now, when you actually construct a classpath in practice, it's also always for a subgraph, right? So really instead of requesting a classpath for a target, we should be constructing a classpath for the full subgraph we're operating over