Challenge: Cultural projects rely on consent that is often informal or scattered across emails.

Solution: Express usage rights as structured policies; commit to them with on‑chain hashes for evidence.

Care: Personal data never needs to be public; only commitments and versions are referenced.

Change: Revocation and scope narrowing are first‑class features, not afterthoughts.

Interoperability: Policies map to familiar licenses so partners can reason about them.

Education: Templates and examples reduce friction for everyday use.

• Structured policy schemas
• Hashed commitments
• Change logs & revocation
• Scoped access
• License mappings

Outcome: Clear expectations and fewer conflicts over rights.