> For the complete documentation index, see [llms.txt](https://motivlabs.gitbook.io/impulse-dev-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://motivlabs.gitbook.io/impulse-dev-manual/readme.md).

# Understanding Impulse Sync

Sync is at the heart of all things Impulse does. DR, Moving Content, Push Publishing, Auditing, CI/CD etc.., all build on top and around the core of Impulse Sync. In a nutshell, impulse syncs does 3 things:

1. Impulse Consumes ANY Content/Data.
2. Impulse Stores all versions of all time for all Content/Data it has consumed in an agnostic format (**Motation**).
3. Impulse Sends that Content/Data to Any System.

The following diagram explains the impulse sync flow and uses after the name of the service involved in each step the ***Rn*** format (example: *Sync Manager (**R1**)*) to denote the responsibility of the process in each step of the sync flow, the description of each service and responsibilities can be found under the [Services](/impulse-dev-manual/services.md) section. 

<div align="center"><img src="/files/QnLXZ1KzObNhpDUXA8Ft" alt="Sync Flow part 1"> <img src="/files/opC0OnIElsqcYJnJBoqF" alt="Sync Flow part 2"> <img src="/files/HQ2EaOu8cR8zxb2U9N9q" alt="Sync Flow part 3"></div>

### Download  the full Flow Chart Below

{% file src="/files/82vBUudfEic8cEY8oYsn" %}
Complete sync flow diagram
{% endfile %}