Lore is a version control system built around Merkle trees and an immutable revision chain. Every change to a repository becomes a new “node” in that chain, content‐addressed by hash. The design targets large, binary‐heavy projects—think game assets or media files—so it stores blobs and trees separately and only pulls data on demand. That means you don’t have to clone gigabytes of unused files to see the latest commit. Under the hood, Lore centralizes control: there’s a single server that tracks all revisions. Clients request pieces of the Merkle tree as needed, so you get lightning-fast initial fetches and near-instant diffs, even on massive repos. Deduplication happens at the storage layer. If two files—say, a texture or audio clip—share identical chunks, Lore writes them just once. That slashes disk use and speeds up backups. Epic Games hosts a gallery of public Lore repositories on GitHub. You’ll find samples that demonstrate workflows for large-scale projects: asset pipelines, automated builds, incremental backups. Each repo shows real-world patterns for branching, tagging, and binary patching. Skimming through them gives you practical insights into how Lore handles merges, conflict resolution, and history queries at scale.