Is it possible to emit an output from a rule but effectively force the input key for that output to be something other than the rule's inputs? Concrete scenario: I perform an external resolve, which involves a lot of dependency and conflict resolution and whatnot. But I also learn some more narrowly "keyed' facts: e.g. this exact Maven coordinate corresponds to this exact

Digest

of a downloaded jar. It would be useful if I could inform the engine of that relationship so that later resolves, with different inputs and therefore different keys, could still take advantage of that

coor -> Digest

relationship and potentially avoid refetching