Any Social Agent can have multiple instances of solid storage. They can also have as many Data Registrations for some specific Shape Tree (eg. Project).

Data Grant with AllInstances scope would still point to some specific Data Registration interop:hasDataRegistration. Even if user creates one Data Grant per existing Data Registration (for Projects). As soon as they add new storage with another Data Registration (for Projects) it would not be covered by existing Data Grants.

I think we can address it simply by using Remote Data Grant with scope `AllRemoteFromAgent'. Alice would maintain a Remote Agent Data Registration for herself, just like she maintains one for any social agent sharing data with her. Diagram below illustrates it.

We would just need to emphasize that remote doesn't mean owned by another agent but data registry (with actual data) is located somewhere else. I think it may be good idea in general to add owner reference to data grants, especially for cases like #100 where social agent issuing the grant is different than one owning the data (I may create separate issue for it).

Another advantage I see with maintaining Remote Agent Data Registration for oneself is opportunity to set limits on one's own access. Alice could issue Data Grants for her self to set her own access to 'read-only' for some scope, she would not need to worry about unintentionally writing to data in that scope. She could always modify her own permissions but that would require explicit operation via her Authorization Agent.