> 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/technical-building-blocks/data-sovereignty-and-trust/access-and-usage-policies-and-enforcement/guiding-questions.md).

# Guiding Questions

{% hint style="success" %}
**Purpose:** Define common baseline policies while allowing participants to set stricter rules within their domains.
{% endhint %}

1. **Policy Scope & Governance**

* *Which common access and usage policies will the data space enforce platform-wide?*
* *What is the minimum baseline for policy enforcement (security, privacy, sustainability criteria)?*
* *Can participants define stricter policies within their own DUGs?*

{% hint style="success" %}
**Purpose:** Specify shared registries and consent points that integrate with identity and trust services.
{% endhint %}

2. **Policy Information Points (PIPs)**

* *Which shared PIPs should the data space maintain (e.g., GDPR consent registry)?*
* *How will PIPs integrate with the Trust Framework and Identity Management?*
* *Should sector-specific consent management be centralised or left to DUGOs?*

{% hint style="success" %}
**Purpose:** Enable machine-readable policy agreements, revocations, and checks throughout the data lifecycle.
{% endhint %}

3. **Policy Lifecycle & Negotiation**

* *How will machine-readable agreements be negotiated (ODRL templates, bilateral APIs)?*
* *At what points in the data transaction lifecycle will policy checks occur?*
* *How will policy revocations be propagated across participants?*

{% hint style="success" %}
**Purpose:** Design a distributed or centralised enforcement system using standard policy decision and enforcement points.
{% endhint %}

4. **Enforcement Architecture**

* *Will the data space operate a central policy engine or federate enforcement to participants?*
* *How will the PEP/PDP/PIP/PAP architecture be implemented in multi-cloud or hybrid environments?*
* *What contextual data (identity, contract terms, asset metadata) will be required for decisions?*

{% hint style="success" %}
**Purpose:** Provide audit trails, retention rules, and real-time alerts to ensure accountable policy enforcement.
{% endhint %}

5. **Compliance Tracking & Proof**

* *How will audit trails be generated, stored, and accessed?*
* *What is the retention period for enforcement proof?*
* *How will the data space support real-time policy breach alerts?*
* *Will conformance evidence (logs, proofs, certificates) be published to support audits and marketplace listing requirements?*

{% hint style="success" %}
**Purpose:** Align policies with trust, identity, and legal frameworks to create a coherent enforcement ecosystem.
{% endhint %}

6. **Interlinkages & Dependencies**

* *How will Access & Usage Policies integrate with the Trust Framework?*
* *How will identity attestations influence policy enforcement?*
* *Which parts of the Legal Building Blocks must be mirrored technically here?*
* *How will policy outcomes be reflected in discovery/marketplace visibility (e.g., eligibility, access tiers)?*


---

# 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/technical-building-blocks/data-sovereignty-and-trust/access-and-usage-policies-and-enforcement/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.