Branches

Branches let you work on changes without affecting the main product model. Think of a branch as your own private copy of the graph where you can experiment, restructure, or draft new sections — and then merge back (or discard) when done.

The main branch

Every workspace starts with a main branch. This is the canonical product model — the version your team considers current and authoritative.

You should avoid making experimental or in-progress changes directly on main. Use a branch instead.

Creating a branch

1. Open the Branches view from the left sidebar (the git-branch icon)
2. Click New Branch
3. Give it a descriptive name — e.g. add-fraud-detection, refactor-checkout-domain, q3-roadmap
4. Click Create

The new branch starts as an exact copy of the current state of main (or whichever branch you fork from). Changes you make on the new branch do not affect main until you merge.

Note

Branches are cheap — there is no cost to creating many. Create a branch for every meaningful chunk of work.

Switching branches

The branch selector at the top of the left sidebar shows the active branch. Click it to open the branch list and switch.

When you switch branches:

• The entire graph view, AI suggestions, search results, and history all reflect the selected branch
• Your uncommitted working state follows you (it’s scoped to your session, not the branch)

Working on a branch

Everything works the same on a branch as on main. Create nodes, edit them, run commits — all scoped to the branch.

When you’re done and the branch is ready to be reviewed or merged, create a merge request. See Merge Requests for the full flow.

Branch list

The Branches page shows all branches in the workspace, organized as a tree that reflects their fork relationships.

Each branch entry shows:

• Branch name and description
• The commit it was forked from
• Whether there are uncommitted changes on it
• Creation date and author

Archiving a branch

When a branch is no longer active — because it was merged, superseded, or abandoned — you can archive it:

1. In the Branches list, find the branch
2. Click the three-dot menu → Archive

Archived branches are hidden from the active branch list but their history is preserved. You can restore an archived branch at any time.

Deleting a branch

To permanently delete a branch, click three-dot menu → Delete. Deletion is only possible if the branch has no unmerged commits — Specor won’t let you accidentally discard work.

Common branching patterns

Pattern	When to use
Feature branch	Adding a new capability or feature set (add-auth-flows)
Refactor branch	Restructuring existing nodes without changing meaning (restructure-onboarding)
Draft branch	Exploring ideas that aren’t confirmed yet (draft-q3-ideas)
Release branch	Snapshotting the product definition for a specific release cycle