> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jedify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Context Graph Versioning

> Review, test, and publish changes to your Context Graph - and restore any earlier version - from inside Jedify.

Context Graph Versioning gives you control over how your Context Graph changes. Every edit is reviewed and can be tested against real prompts before it goes live, and any recent version can be restored - all from the Jedify app.

This works because your Context Graph is stored as a Git-managed, text-based (YAML) structure.

## What you get

> [card] Review
>
> Every edit is reviewed before it reaches **main**, with a side-by-side YAML diff.

> [card] Roll back
>
> Restore any version published in the last 90 days.

> [card] Compare
>
> While previewing a branch or an earlier version, every node offers a **Compare to main** view.

> [card] Audit
>
> See who pushed each branch and when, and who merged each change into **main**.

## How a change reaches production

Changes move through five stages:

| Stage | What happens |
| - | - |
| **Edit** | A skill run opens an edit session. |
| **Push** | Commits land on a dedicated branch. |
| **Preview** | The branch is available as a read-only preview, shown with a purple frame. |
| **Review** | A YAML diff against **main** is available; the branch is merged or declined. |
| **Publish** | The branch closes and a new version goes live on **main**. |

Merging a branch publishes a new version on **main**. See [Review, merge, and restore](https://docs.jedify.com/semantic-fusion/versioning/review-and-merge.md) for what the review screen shows.

## Rollout

Once Context Graph Versioning is enabled for your account, two things change:

* Context Graph edits go through **skills** instead of the UI.
* The Context Graph is stored as a file-based, Git-backed structure.

## What stays editable in the UI

Not everything moves to skills. You can still edit the following directly in Jedify:

* **Knowledge** - Business Glossary and Research Agent Guidance.
* **Test sets**.
* **Dimensions** - new dimensions are still created in the UI and approved through the regular process.

> [!NOTE]
>
> Dimensions created after Context Graph Versioning is enabled do not appear in the node's YAML file.

## Storage

In the first release, entities are migrated to YAML: one file per node, plus a single file for all relations. Dimensions are versioned in Git but are not YAML files - converting them is planned for a later release.

## Repository ownership

You have two options, and you can switch between them at any time:

* **Jedify-managed** *(default)* - a Git repository managed by Jedify and hosted on Jedify's S3. No GitHub setup required.
* **Your own GitHub** - connect a GitHub account and move the repository into that environment. See [Connect a GitHub repository](https://docs.jedify.com/semantic-fusion/versioning/github.md).

## Conflicts

Conflict resolution happens in the skills or on GitHub - not in the Jedify app.

> [card] [The Versions menu](https://docs.jedify.com/semantic-fusion/versioning/versions-menu.md)
>
> Browse branches and published versions, and switch what you're viewing.

> [card] [Review, merge, and restore](https://docs.jedify.com/semantic-fusion/versioning/review-and-merge.md)
>
> Compare a branch to main, publish it, or roll back.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.