> 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-interoperability/provenance-traceability-observability/guiding-questions.md).

# Guiding Questions

{% hint style="success" %}
**Purpose:** Capture regulatory and business needs for data lineage to support compliance and value-added services.
{% endhint %}

1. **Requirements & Use Cases**

* *Which legal, contractual, or sectoral requirements exist for provenance and traceability?*
* *Are there AI Act or other regulatory triggers that mandate detailed data lineage or traceability?*
* *Are there business cases for using provenance data to add value (e.g., sustainability claims, quality certification)?*

{% hint style="success" %}
**Purpose:** Adopt or extend existing provenance ontologies to flexibly represent traceability information. 
{% endhint %}

2. **Data Modelling**

* *Will existing ontologies (e.g., W3C PROV-O, PAV) be adopted and extended for sector needs?*
* *Should provenance be modelled as “events” (e.g., CloudEvents) for flexibility?*

{% hint style="success" %}
**Purpose:** Define storage, retention, encryption, and access policies for provenance data across participants. 
{% endhint %}

3. **Storage & Management**

* *Will provenance/traceability data be stored locally by participants, by certified 3rd parties, or in a hybrid model?*
* *What are the retention, encryption, and access control policies?*

{% hint style="success" %}
**Purpose:** Clarify which processes and telemetry data should be observable for governance and monitoring purposes. 
{% endhint %}

4. **Observability Scope**

* *Which Control Plane activities (catalog publication, contract negotiation, transfer process) will be observable?*
* *Will operational telemetry (uptime, performance) also be included under the same governance?*

{% hint style="success" %}
**Purpose:** Designate certified observability providers while avoiding centralization and systemic risks.
{% endhint %}

5. **Trust & Third Parties**

* *Which organisations could act as certified observability service providers?*
* *How will centralization risks be mitigated?*

{% hint style="success" %}
**Purpose:** Integrate provenance and traceability rules into the rulebook under governance oversight.\
**Governance Linkages**
{% endhint %}

6. **Governance Linkages**

* *How will rules for provenance and traceability be reflected in the rulebook?*
* *Which governance body will approve changes to provenance and traceability standards or processes?*


---

# 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-interoperability/provenance-traceability-observability/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.