> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/impl-eidas-wallet/development/12.-related-and-additional-material.md). # 12. Related and Additional Material A complete implementation effort should use a library of reference material starting with: * GovStack Wallet Building Block specification and associated API documentation. * GovStack Identity, Consent, and Electronic Signature specifications for neighbouring components. * GovStack Cross‑Functional Requirements for security, logging, monitoring, and availability. * The EUDIW Architecture Reference Framework, including OpenID4VCI and OpenID4VP profiles. * Regulation (EU) 2024/1183 (eIDAS 2.0), the GDPR, the Cybersecurity Act, and relevant national acts and regulations. Templates for DPIAs, procurement language, architecture diagrams, test plans, and incident response playbooks are helpful companions. Maintaining these alongside the Wallet Implementation Guide and updating them as profiles, standards and laws evolve will make it far easier for future teams to continue the work without losing consistency or compliance. --- # 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://specs.govstack.global/impl-eidas-wallet/development/12.-related-and-additional-material.md?ask=&goal= ``` `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.