The Trustflows charter pushes a clear direction: make trustworthy, interoperable, legally compliant, user-centric data sharing the default, by building architectures that are write-to-read, separate storage/identity/authorization, and publish reusable assets (vocabularies, shapes, interaction patterns, developer docs). In practice, teams struggle with: “Did we actually implement these principles?” and “Can others reuse what we produced without re-interpreting it?” Trustflows already points at concrete building blocks (e.g., Trust Envelopes, policy engines using ODRL, verifiable credentials, UMA-style separation) but there is no widely usable conformance/validation toolchain that checks designs and implementations against these principles. Website: https://trustflows.eu
Core research question: How can we formally and automatically verify that a data-sharing solution (assets + flows) conforms to the Trustflows charter properties and Trustflows architecture requirements? Possible outcomes are: a test framework, a linter tool, an evaluation of real use cases we’re working on,