> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/ai-systems/transparency-notice.md). # Transparency notice A transparency notice (or information notice) is a crucial document for informing users and stakeholders about the operation and use of AI systems. This notice aims to ensure that AI systems are transparent, accountable and respect the fundamental rights of individuals. In Dastra, you need to integrate this manual into the "Attachments" section of an AI system. You can upload it as a document, or write it directly in the tab. The notice generated by the AI assistant can be exported as PDF, Word, HTML or Markdown, from the notice assistant or from the **Export information notice** action of the AI system record. In the export window, the **Add this file to the attachments of this AI system** option, enabled by default, adds the exported file to the attachments of the "Documentation" step; each export creates a new attachment.

Transparency notice export window with the option to add the file to the attachments — Adding the exported notice to the attachments of the AI system

--- # 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://doc.dastra.eu/en/features/ai-systems/transparency-notice.md?ask=&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.