> 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/detailed-descriptions/functional.md).

# Functional

This section details the Trust Framework's functionality.

The [use cases depicted in earlier chapters](/version-3.0/use-cases.md) are only a selection of the iSHARE Trust Framework's full use case scope. This scope is based on [three 'primary' use cases](/version-3.0/detailed-descriptions/functional/primary-use-cases.md):

1. Machine-to-Machine service provision;
2. Human to Machine service provision with authorisation and identity info held at the Service Provider;
3. Human to Machine service provision with identity info held at the Identity Provider.

These primary use cases have several 'derived' use cases which cover all possible uses.

The primary use cases are supported by '[secondary' use cases](/version-3.0/detailed-descriptions/functional/secondary-use-cases.md), which include processes related to registration and processes that recur in primary use cases. This section is concluded by functional requirements - those [per role in the scheme](/version-3.0/detailed-descriptions/functional/functional-requirements-per-role.md) and those for the iSHARE [user interface](/version-3.0/detailed-descriptions/functional/functional-requirements-per-role/user-interface-requirements.md) in H2M use cases.


---

# 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/detailed-descriptions/functional.md?ask=<question>&goal=<user_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.