> 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="https://1268830422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_6b8AnMjM58FWM_iK%2Fuploads%2FErJ1lnrhShgJEwuwe0Ew%2Fsync-flow1.png?alt=media&amp;token=8a674d51-74e5-4f08-8c9a-8df75b1d0be5" alt="Sync Flow part 1"> <img src="https://1268830422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_6b8AnMjM58FWM_iK%2Fuploads%2FGNhpsJ4ONjR6l8JtjHr7%2Fsync-flow2.png?alt=media&amp;token=16d13c40-8bd9-4d92-a0ad-1bbe7a8ba1bf" alt="Sync Flow part 2"> <img src="https://1268830422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_6b8AnMjM58FWM_iK%2Fuploads%2FxT88MjJho6EKmcDatK0t%2Fsync-flow3.png?alt=media&amp;token=c546001c-8e8b-435e-98ef-9cfe3edeb715" alt="Sync Flow part 3"></div>

### Download  the full Flow Chart Below

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