# Care flow components as code
URL: https://docs.awellhealth.com/docs/data/components

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



When a care flow syncs to the repository, its components are written as **JSON files** in a fixed folder
structure.

> **This structure is experimental.** Awell may change it substantially without prior notice, so don't
> build tooling that depends on the exact shape without expecting to maintain it.

## Folder structure: one file per component kind [#folder-structure-one-file-per-component-kind]

```
repository
├── actions/actions.json
├── data_point_definitions/data_point_definitions.json
├── labels/labels.json
├── messages/messages.json
├── pathways/pathways.json
├── rules/rules.json
├── settings/settings.json
├── stakeholders/stakeholders.json
├── steps/steps.json
└── …
```

The split keeps a diff readable: a change to a message shows up in `messages.json` rather than buried in
one enormous document.

## What the files contain [#what-the-files-contain]

* **actions**. The actions in the care flow, including API calls.
* **data\_point\_definitions**. The data point definitions, matching the
  [data catalog](/docs/data/data-catalog).
* **messages**. Message content.
* **pathways**. The care flow definition itself.
* **rules**. The conditional logic.
* **settings**. Care flow settings.
* **stakeholders**. Who the care flow's actions are assigned to.
* **steps**. The steps and their structure.
* **labels**. The [step labels](/docs/design-care-flows/label-your-steps).

The folder names use Awell's internal vocabulary: `pathways` holds what the product now calls care flows.
See [Key terms](/docs/get-started/key-terms).

## Editing these files does not change the care flow [#editing-these-files-does-not-change-the-care-flow]

The sync is one-way. See [How syncing works](/docs/data/syncing-to-scm).

## Next steps [#next-steps]

Back to [Data & source control](/docs/data).