Where Lore is native today
- Binary parity (no LFS bolt-on) — also a TOVIO v1 design target
- BLAKE3 content addressing — also a TOVIO v1 design target
- Open specification, no vendor lock-in — also a TOVIO v1 design target
Comparison · Lore
Lore vs Git vs TOVIO
Lore is Epic Games' open-source (MIT) version control system for binary-heavy projects, released in June 2026 with BLAKE3 content addressing and a centralized design. Here is how it compares with Git and with TOVIO's design, row by row.
How to read this
native / first-class partial or workaround not supported
Lore and Git cells reflect a 2026 snapshot of each tool's publicly documented behavior and will change as those projects evolve; where another system genuinely leads a row, the table shows it. TOVIO cells reflect the v1 design target — TOVIO is pre-1.0, unpublished, and not yet independently audited. See the launch gates and what ships today for current implementation status.
Against the systems reinventing the model
$against the systems reinventing the model2026 snapshot · TOVIO = v1 design target
| Capability | Lore | Git | TOVIO |
|---|---|---|---|
| Offline-first, fully distributed | Partial or workaround | Native or first-class | Native or first-class |
| Per-file cryptographic permissions | Not supported | Not supported | Native or first-class |
| AI-agent capability tokens | Not supported | Not supported | Native or first-class |
| Agent commit provenance | Not supported | Not supported | Native or first-class |
| Change-centric identity (survives rebase) | Not supported | Not supported | Native or first-class |
| First-class conflict objects | Not supported | Not supported | Native or first-class |
| No staging area | Not supported | Not supported | Native or first-class |
| Binary parity (no LFS bolt-on) | Native or first-class | Not supported | Native or first-class |
| BLAKE3 content addressing | Native or first-class | Not supported | Native or first-class |
| Lane pointers auto-reconcile when offline copies diverge | Not supported | Not supported | Native or first-class |
| Full operation log / undo-anything | Partial or workaround | Partial or workaround | Native or first-class |
| Semantic diffs & behavioral versioning | Not supported | Not supported | Native or first-class |
| Open specification, no vendor lock-in | Native or first-class | Native or first-class | Native or first-class |
What the rows say
What TOVIO's design adds
- Offline-first, fully distributed — partial or a workaround in Lore
- Per-file cryptographic permissions — not supported in Lore
- AI-agent capability tokens — not supported in Lore
- Agent commit provenance — not supported in Lore
- Change-centric identity (survives rebase) — not supported in Lore
- First-class conflict objects — not supported in Lore
- No staging area — not supported in Lore
- Lane pointers auto-reconcile when offline copies diverge — not supported in Lore
- Full operation log / undo-anything — partial or a workaround in Lore
- Semantic diffs & behavioral versioning — not supported in Lore