Branches work like git. On data.
Fork, commit, diff, merge — on a graph. Every commit stays queryable.
Software solved collaboration with branches and history. Legra gives data the same workflow: people and agents work on forks, hand them on, and merge when the rules are satisfied.
Branch
Fork production, or any branch, in constant time. Copy-on-write: the fork shares every unchanged page.
Commit
Immutable, signed, content-addressed. A commit names the graph state and who made it.
Diff
Quads added, quads removed, between any two commits or branches.
Merge
Three-way merge on the graph. Conflicts are named; history keeps both parents.
Complex work happens on a fork. Production never notices.
An agent forks production, does the work — including what-if scenarios — and hands the branch on. Merge comes when everyone is satisfied and SHACL passes.
- 01
Fork the branch
An agent or a person forks production — or any branch — and works there. The source branch stays as it was.
- 02
Do the work, including what-if
Complex changes, experiments, and alternative scenarios live side by side as branches and compare by diff.
- 03
Hand over
The branch passes to the next person or agent in the workflow — as many steps as the work needs.
- 04
Satisfy the rules
SHACL validation and every party's sign-off are the gate. No approver bottleneck by design.
- 05
Merge
By hand or automatically once the gate is clear. The journal records who, under whose authority, with what result.
Ask the graph what it knew last March.
Every commit stays addressable. A query against any past state costs what a cold query costs today: no snapshots, no restores, no second copy.
- Commit 3f9a · today
- Current answer
- Commit 8c21 · last quarter
- What the graph knew then
- Commit 1e07 · the audit date
- What the auditor saw
Content-addressed pages are shared across commits, so history costs storage only where the graph actually changed.
History with evidence.
Signed and encrypted
Every commit is signed; every block is encrypted with workspace keys. Custodians replicate ciphertext.
Journaled
Tasks, decisions, costs, and derivations sit next to the commits they produced.
Agent-native
Agents get a fork, a task, a budget, and scoped authority. Their work merges like everyone else's.