> For the complete documentation index, see [llms.txt](https://changes.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changes.ishare.eu/readme.md).

# iSHARE Change Management

Welcome to the documentation of iSHARE's Change Management process.

* For more information regarding iSHARE, please refer to iSHARE's [website](https://www.ishare.eu)
* For more information about the change management process as part of the [iSHARE Trust Framework](https://framework.ishare.eu) refer to [this page](https://framework.ishare.eu/detailed-descriptions/operational/operational-processes/change-management)

The change management process is the responsibility of the Scheme Owner (iSHARE Foundation), working together with the Change Advisory Board.

Please review the pages about the [RFC process](/change-management-process.md) and the [impact analysis procedure](/impact-analysis-procedure.md) to understand more about the process.

All documentation about the organised meetings (CAB and Co-Creation Meetings) is kept in [Co-Creation and CAB Meetings](https://changes.ishare.eu/v/cab-and-deepdive-meetings). Impact analysis of RFCs are kept [here](https://changes.ishare.eu/v/rfc-impact-analysis-1). A complete overview of all RFCs, their status and priority, is kept is as [Gitlab issue board](https://gitlab.com/ishare-foundation/cab/rfc/-/boards).


---

# 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://changes.ishare.eu/readme.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.