Version Control Primitive

Git.
For knowledge.

Fork your memory before a risky experiment. Merge what worked. Roll back what didn't. Every state of your intelligence is addressable, auditable, restorable — and the Dream Engine runs on any branch you point it at.

The operations you already know.

If you've used git, you already know Branches. Six primitives, same semantics, applied to knowledge instead of code.

branch
Create a branch
Fork memory at the current snapshot. Experiments don't pollute main.
checkout
Switch branches
The Dream Engine now runs against the branch you chose. Queries return that branch's truth.
diff
Diff two branches
See exactly what's different — which memories, which edges in the graph, which insights.
merge
Merge into main
Conflict resolution when two branches edited the same memory. Three-way merge, auto or manual.
snapshot
Snapshot the current state
Immutable, addressable. Automatic before dream cycles. Manual when you want.
rollback
Roll back to a snapshot
One API call. Your memory rewinds to the state at that point in time. Fully reversible.

A DAG of knowledge states.

Every snapshot is a node. Every branch is a pointer. Just like git — except the objects are memories, not blobs.

* main d81f4a After nightly dream cycle (127 ops) <HEAD> | | * what-if-no-ambient 3c9e11 Removed ambient captures |/ * a0713b Weekly baseline snapshot | | * experiment-q2-pivot b44f88 Rewrote @Decisions for Q2 |/ * f10d20 After Obsidian vault import (847 ops) | * 4aa1c3 Initial

Experiment without fear.

Three use cases that become trivial once memory is versioned.

Pivot safely
Fork a branch for a new market thesis. Let the Dream Engine run there for a week. If it stalls, switch back. If it compounds, merge.
Counterfactual analysis
"What if we'd removed this @Decision 3 months ago?" — roll back, dream, compare outcomes, then merge or discard.
Agent isolation
Give each experimental agent its own branch. Compare which agent's memory evolved more coherently. Promote the winner.

Production characteristics.

O(1)
Branch create
Copy-on-write refs
90d
Snapshot retention
Unlimited on Scale
DAG
Storage model
Merkle-indexed
<2s
Rollback latency
p95, any snapshot

Your memory deserves version control.

Every consolidation is a checkpoint. Every branch is a hypothesis. Every snapshot is an undo button.

Start Free Read the docs