Lore (version control)
Epic Games’ open-source (MIT, Rust) next-generation revision-control system — a Git alternative built for repositories that mix code with large binary assets, the games/entertainment workflow Git handles badly. The version-control layer of developer-tooling.
What it is
- Content-addressed Merkle-tree storage with chunked files and on-demand hydration — you fetch only the chunks you need, so huge binary assets don’t force full-history downloads.
- Lightweight branching and an immutable, signed revision chain (integrity + provenance of history).
- It’s the built-in VCS for UEFN (Unreal Editor for Fortnite), though the open-source build differs from the proprietary UEFN one. Pre-1.0.
Why it’s here — and the cross-spoke tie
Lore is the spoke’s version-control corner and another instance of the founding thread (synthesis): rebuild an established developer-tooling layer in a systems language (Rust) to fix a structural weakness — here, Git’s poor handling of large binaries — rather than chasing raw compile speed like the TS compiler. The asset-versioning focus gives it a real game-engines-wiki adjacency (it versions Unreal/UEFN content pipelines), but Lore is general-purpose dev infrastructure, not an engine — so it lives here and cross-links rather than routing into that spoke.
Tier
T1 — first-party Epic Games repo. freshness: volatile — pre-1.0, so design and feature set are
still moving; claims are the project’s own.
Related
developer-tooling · git · geschichte · typescript-7-go-compiler · yaff · synthesis