> For the complete documentation index, see [llms.txt](https://framework.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.ishare.eu/version-3.0/main-aspects-of-the-ishare-trust-framework/key-functionality/provide-a-trust-framework.md). # Provide a Trust Framework Within the iSHARE network, it is the explicit aim to define trust based on a synthesis between technological and legal aspects. In practical terms, the aim is to let iSHARE participants interact within the network through a party that they know and trust (their Participant Registry) and sign one contract, based on which they have a contract with all participants within the data space/iSHARE network. In other words, participants within the data space/iSHARE network do not need to sign separate contracts with each other to share data with each other (although they are free to define additional contracts that do not conflict with the iSHARE Trust Framework). An important tool within the Trust Framework is licenses, which define the conditions under which data can be exchanged or services can be consumed. For functional details on licenses, see the [Licenses page](/version-3.0/detailed-descriptions/functional/licenses.md). The Trust Framework is depicted under [Primary use cases](/version-3.0/detailed-descriptions/functional/primary-use-cases.md) and needs an appropriate technological underpinning so that parties can authenticate each other in a reliable way. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://framework.ishare.eu/version-3.0/main-aspects-of-the-ishare-trust-framework/key-functionality/provide-a-trust-framework.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.