> For the complete documentation index, see [llms.txt](https://docs.sygnal.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sygnal.network/reference/feedback.md). # How to give feedback How to ask questions, report problems and propose changes to Sygnal and its documentation. Sygnal is developed in the open, and feedback shapes it. This page explains where to send it. ## Something in the docs is unclear or wrong [Open an issue](https://github.com/Medtronic-LABS/sygnal/issues/new?template=docs-unclear.md) and link to the page. Say what confused you; a suggested wording helps but isn't needed. If you're comfortable with GitHub, you can also suggest the fix directly as a pull request. Every page lives in the repository's [`docs/`](/readme.md) folder. ## A question about the specification [Ask a question](https://github.com/Medtronic-LABS/sygnal/issues/new?template=spec-question.md). Tell us which API, schema or field it's about, and what you're building. Answers that would help others go back into the documentation. ## A change to the specification [Propose a change](https://github.com/Medtronic-LABS/sygnal/issues/new?template=change-proposal.md). Describe the problem first, ideally with a real use case, then the change you suggest. Proposals are discussed in the open before they are accepted. Accepted changes are recorded in the [changelog](/specification/changelog.md). ## Open design questions Some parts of Sygnal are still being designed. They are listed on the [Open questions](/reference/open-questions.md) page. Views on any of them are welcome: open an issue and name the question in its title. ## Partnerships, pilots and the sandbox * To discuss a pilot, a partnership or joining the [Sygnal Sandbox](/build-and-join/sandbox.md), email . * For help once your platform is connected to the sandbox, email . ## What happens to your feedback * Issues are read and labelled, and we aim to reply to each one. * Fixes to the docs are made as they come in. * Changes to the specification follow the steps above and are listed in the changelog, so you can see what changed and why. See also [Contributing](/reference/contributing.md) for how to make changes yourself. --- # 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://docs.sygnal.network/reference/feedback.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.