Sounds like you're thinking of a slightly different repository concept. A MavenRepository for example sounds like an external place not under our control where the original content is pulled from. Not a location under the control of the server or DC where it stores content.
Which tells me my repository idea is really flawed, since I saw it as either a purely internal location (e.g. server/data/deployments where content provided through the API is copied for server use) or an unholy mix of internal/external (e.g. a deploy/ dir with a scanner thread detecting changes and deploying them.)