infrastructure · versioned

Git-backed Canvas.

The canvas is underlaid with Git. Every change to your workflow is versioned — so you can diff, branch, review and roll back your canvas exactly like code.

In development MIT · self-hosted .dispatch/graph.json

what it is

Your canvas is a file. Git versions it.

Every DISPATCH canvas serialises to a plain, human-readable graph.json. Git tracks that file, so the whole canvas inherits real version control — a history of every node added, every edge rewired, every model swapped.

stable serialisation

Meaning, not jitter.

Nodes and edges are stored as ordered, line-addressable text. A two-pixel nudge produces no diff; rewiring Plan → Create produces exactly one.

semantic diffs

Review intent, not coordinates.

The diff speaks canvas: + Review gate, − Doc node, ~ Create gpt-4o → claude-opus.

branch & roll back

Try a graph. Throw it away.

Branch to explore a parallel orchestration. Like it? Merge. Don't? git reset to any earlier commit and the nodes snap back.

interactive · version history

Walk the history of one canvas.

Click any commit to load that revision — the diff and canvas state both jump to it. Open a branch, then roll HEAD back to any point.

branch:main · HEAD →a1f9c0e

commit log 5 commits

canvas at this commit a1f9c0e

graph.json +0 −0

on main · 5 commits · working tree clean · versioned

Replay of a real commit history. A live canvas commits on every meaningful edit.

how it works

Git, underneath the pixels.

Nothing leaves your machine. The repo lives in your project, beside the rest of your code, and uses the Git you already trust.

autocommit on edit ·local repo ·plain git

01 · serialise

The canvas writes graph.json

Every node and edge serialises to a stable, ordered file. Layout-only moves stay out of tracked content, so history records meaning, not jitter.
02 · commit

Edits become commits

Add a Review gate, swap a model, fan out a Parallel block — each lands as a tidy, message-tagged revision. Or commit by hand, your way.
03 · branch & review

Explore in parallel, review like code

Branch to try an alternative orchestration without touching main. The semantic diff shows exactly what changed, so a teammate can review the canvas in a PR.
04 · roll back

Reset the canvas to any commit

A wrong turn is one checkout away. Point HEAD at an earlier commit and the live canvas rebuilds to that exact state — nodes, wiring, models intact.