> 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/about.md).

# About Sygnal

Who develops Sygnal, who runs the hosted services, and how stewardship is meant to work.

Sygnal is an open way to build Care Coordination Networks: networks in which independent health platforms hand off care, follow each handoff through, and see where care falls through the gaps. See [Welcome to Sygnal](/readme.md) for an overview.

## Who shapes the protocol

The **Sygnal Protocol** is shaped together, in the open. **Medtronic LABS** leads the work, with partners, implementers and the wider community. The specification and documentation are public: anyone can review them, use them and propose changes. See [How to give feedback](/reference/feedback.md).

## Who builds the platform

**Medtronic LABS** develops the **Sygnal Platform**, the open-source software that implements the protocol. Anyone will be able to run it once it is released.

## Who runs the hosted services

**Medtronic LABS** operates Sygnal Network Services today. The operator may change as network governance develops. See [Protocol, platform and services](/concepts/protocol-platform-services.md).

## Who looks after the standard

Medtronic LABS looks after the specification for now, on behalf of everyone who takes part. The intent is that no single organisation owns the standard: stewardship is meant to move to a neutral governance body as adoption grows. See [Network governance](/governance/governance.md#stewarding-the-specification).

## Licence

The Sygnal specification and documentation are published under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). You may share and adapt them, including commercially, if you give credit and share adapted versions under the same licence.

## Get in touch

Email <hello@sygnal.network>. For questions and suggestions about the specification and documentation, see [How to give feedback](/reference/feedback.md).


---

# 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/about.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.
