Self-Sovereign Identity Model Principles: Identifier and Identity Data Usage Licensing

[This is a follow-up to the conversation that started here: https://github.com/solid/specification/issues/217#issuecomment-761859764. Check there for the initial details.]

Context

For example, to fully realize the SSI model in Solid, I not only want to specify access controls but also usage controls (in terms of usage license controls) whereby the consuming app needs to agree to example terms like:

App X can refer to but can not read and persist my content to any external storage system (beyond where the original content currently resides) without my expressed permission.
App X cannot attach it's own ancillary information to my Identity (e.g. WebId) without my expressed permission.
App X can read my content but cannot aggregate it (anonymously or not) to create its own new content without my permission.
etc.

Questions

Is it envisioned that Solid will support these sorts of usage license terms ...as part of an end-to-end lifecycle? Is this type of support weeks, months, or years away? Is it on the roadmap?

Is there anything that needs to be changed in the current Solid architecture to support usage license terms? ...or has Solid been architected to make usage license terms a relatively straight forward design/implementation detail?

Best regards,
Michael Herman
Self-Sovereign Blockchain Architect
Trusted Digital Web Project
Hyperonomy Digital Identity Lab
Parallelspace Corporation

Start with the initial details in issue 217's linked comment, then review the current Solid specification and architecture material. Done would be a documented determination of whether usage-license terms are supported, require architectural changes, or belong on the roadmap.