Does Gradle include any sort of filesystem abstraction?

A sort of out-of-left field question, I expect, but …

Does Gradle have any sort of abstraction layer over the filesystem? Suppose, for example, that I wanted to store the results of a task, or its inputs, in a database rather than directly on the filesystem?

I’m thinking specifically of a case where I might have several tasks operating on an XML document or large JSON data structure. I’d like to be able to store intermediate results in some sort of in-memory store so that they didn’t have to be serialized and parsed at each task boundary.

This probably flies in the face of the up-to-date checking that Gradle does with filesystem checksums, but I thought it was worth asking.