> For the complete documentation index, see [llms.txt](https://template.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://template.ishare.eu/business-and-organisational-building-blocks/business-building-blocks/data-space-intermediaries-and-operators/guiding-questions.md).

# Guiding questions

{% hint style="info" %}
**Purpose of this Building Block Component:** Intermediaries and operators play a crucial enabling role, making data accessible, trustworthy, and compliant with EU regulations. They help reduce complexity and lower barriers to entry for participants.

Key responsibilities may include:

* Identity and access management (e.g. authenticating participants, issuing credentials)
* Service brokerage (e.g. data search and matchmaking)
* Compliance assurance (e.g. ensuring data usage aligns with CSRD, EPBD, or GDPR)
* Onboarding and support for participants, especially SMEs and municipalities

Operators might include neutral industry bodies, domain-specific hubs, or trusted IT providers. Multiple operators can coexist under federated rules, enabling sectoral specialisation while ensuring interoperability through shared frameworks. 
{% endhint %}

{% hint style="success" %}
**Purpose:** Authentication mechanisms (e.g., credentials issuance, federated logins). Clear participant identity verification.
{% endhint %}

1.  **Identity & Access Management**

* *How will participants be authenticated (federated identity, credentials)?*
* *What trust anchors or standards will be used?*

{% hint style="success" %}
**Purpose:** Data discovery and matchmaking between providers and users. Efficient search and service recommendation systems.
{% endhint %}

2. **Service Brokerage**

* *Which discovery functionalities are critical for initial use cases?*
* *Who is responsible for matching data providers with data consumers?*
* *How can intermediaries ensure services scale as participation grows?* 
* *How can intermediaries’ models align with overall data space goals?*

{% hint style="success" %}
**Purpose:** Ensuring data transactions align with regulatory frameworks (CSRD, EPBD, GDPR). Data governance and audit trail management.
{% endhint %}

3. **Compliance Assurance**

* *How will operators enforce compliance (policy engine, audit trails)?*
* *Who will validate that data usage aligns with EU and national regulations?*
* *How can neutrality be ensured while operators comply with rules?*

{% hint style="success" %}
**Purpose:** Dedicated support structures for smooth onboarding. Special focus on SMEs, municipalities, and smaller participants.
{% endhint %}

4. **Onboarding & Participant Support**

* *Which resources or tools facilitate onboarding, especially for smaller or less digitally mature participants?*
* *Who handles participant support, and how is quality assured?*<br>

{% hint style="success" %}
**Purpose:** Sectoral or regional hubs enable specialisation, while interoperability among multiple operators is ensured through common rules.
{% endhint %}

5. **Federation & Specialisation**

* *Will multiple domain-specific operators exist? What are their defined roles?*
* *What mechanisms will ensure interoperability among the federated operators?*
* *What contingency measures ensure continuity if an operator fails?*&#x20;
* *How can dependency risks be mitigated across multiple services?*

{% hint style="success" %}
**Purpose:**  Transparent operational standards ensuring neutrality and trustworthiness of operators.
{% endhint %}

6. **Governance and Trust**

* *What governance rules apply to operators? Are these clearly documented?*
* *How is neutrality and fairness guaranteed across operators?*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://template.ishare.eu/business-and-organisational-building-blocks/business-building-blocks/data-space-intermediaries-and-operators/guiding-questions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.