> 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/build-and-join/build.md).

# Getting started

Where implementers start, depending on what you are building.

## Pick your path

| You are…                                                                                        | Start with                                                                                                                                                                                                                                                                                                                                        |
| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **A platform vendor or implementer** connecting an EMR, community health app or hospital system | The [Sygnal Sandbox](/build-and-join/sandbox.md), the [Edge Adapter](/components/edge-adapter.md) and [Running the reference flows](/build-and-join/running-reference-flows.md). [Joining a network](/build-and-join/joining-a-network.md) gives the steps. An implementer checklist will be published with the first Sygnal Platform components. |
| **A developer** who wants to see the actual messages sent between platforms                     | [Running the reference flows](/build-and-join/running-reference-flows.md) and the [Use cases](/use-cases/use-cases.md)                                                                                                                                                                                                                            |
| **A network operator** setting up the shared services                                           | [Protocol, platform and services](/concepts/protocol-platform-services.md), the [Components overview](/components/components.md) and [Network governance](/governance/governance.md)                                                                                                                                                              |
| **Someone reviewing or extending the specification**                                            | [Specification overview](/specification/specification.md) and [Contributing](/reference/contributing.md)                                                                                                                                                                                                                                          |

## What you need to know first

1. **Handoffs are Beckn.** If your platform can already act as a Beckn seeker or provider, you are most of the way there. See [Transitions on Beckn](/specification/transitions-on-beckn.md).
2. **Everything is signed and asynchronous.** Expect an immediate signed ACK (a "received" reply), then a signed callback. See [Conventions](/specification/conventions.md).
3. **Clinical content stays with you.** The network services get coordination metadata only, as policy permits. Your adapter enforces this. See [Privacy and data minimisation](/concepts/privacy-and-data-minimisation.md).
4. **You raise deviations when you are the one waiting.** Run SLA (service-level agreement) timers for the commitments you depend on. See [Deviations and escalation](/concepts/deviations-and-escalation.md).

## Incremental adoption

You don't need to implement everything at once. A sensible order is:

1. **Join** the network: keys, registry record, adapter. See [Joining a network](/build-and-join/joining-a-network.md).
2. **Handoffs:** directed referrals, with status and deviations carried inside the handoff messages (in-band), as in UC1 and UC2.
3. **Deviations:** raise `deviation/flag` when a step you are waiting for is overdue, and handle `on_flag` outcomes (dispositions).
4. **Policies (when the network has them, at any point from here):** accept `policy/update`, fetch with `policy/get`, and apply the shared SLA rules and data rules. See [Starting without encoded policies](/concepts/policies.md#starting-without-encoded-policies).
5. **Reporting:** send aggregate `event/report` and export network telemetry. Reporting needs a reporting policy.
6. **Signals:** receive `signal/emit` and turn signals into worklist items for the accountable role.
7. **Matched handoffs** through discovery (as in UC3 and UC4), and **shared plans** where relevant.


---

# 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/build-and-join/build.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.