Skip to content

carapace-sh/carapace-bin / skills/lore

Use when working with the Epic Games Lore version control system — a centralized VCS designed for game development with binary-first content-addressed storage. Covers architecture, core concepts, server deployment, CLI and server configuration, workflows, and the full command reference. Triggers on: "lore", "Lore", "Epic Games Lore", "loreserver", "version control system", "VCS", "content-addressed", "immutable store", "mutable store", "BLAKE3", "Merkle tree", "FastCDC", "fragment", "partition", "content-defined chunking", "split-write", "shared store", "revision", "branch", "merge", "cherry-pick", "revert", "bisect", "layer", "link", "lock", "staging", "dirty", "obliterate", "packfile", "LoreError", "config.toml", "cli.toml", "lore://", "Lore server", "Lore CLI", "Lore configuration", "Lore FAQ", "Lore roadmap", "Lore system design".

FileKindSize
SKILL.mdskill md5.9 KB
references/cli.mdmarkdown14.0 KB
references/config.mdmarkdown8.1 KB
references/core-concepts.mdmarkdown11.5 KB
references/faq-roadmap.mdmarkdown5.0 KB
references/overview.mdmarkdown5.8 KB
references/setup.mdmarkdown3.7 KB
references/workflow.mdmarkdown5.9 KB

references/faq-roadmap.md

View on GitHub
# FAQ and Roadmap

Frequently asked questions about Lore and the planned feature roadmap.

> **Source of truth**: <https://epicgames.github.io/lore/faq/> and <https://epicgames.github.io/lore/roadmap/>

## FAQ

### What is Lore?

A next-generation open source version control system from Epic Games, designed for unprecedented scalability — both in data size and the size/distribution of teams. Optimized for projects combining code with large binary assets (games, entertainment). MIT licensed.

### How does Lore differ from Git?

- **Git**: Content-addressed revision graph is excellent, but binary files are second-class — large files require LFS, sparse checkouts have sharp edges in offline use, no native multi-tenant isolation.
- **Lore**: Binary-first (chunked, deduplicated), lazy sparse working trees, fragment-level dedup effective on both multi-gigabyte binaries and kilobyte text files, free branching, full offline operation for staging/committing/branching, partition-level multi-tenant isolation.

### How does Lore differ from Perforce?

- **Perforce**: Handles large binary assets but requires server round trips for everyday operations, proprietary wire protocols, limited binary-level deduplication.
- **Lore**: Centralized server-of-record but offline-capable, content-addressed with fragment-level dedup, open specification and MIT license, QUIC/gRPC protocols.

### What platforms are supported?

Windows, macOS (ARM64), Linux (x86-64, ARM64). Pre-built binaries for all three. Docker image for server deployment. Language bindings: C/C++, Rust, JavaScript, C#, Python, Go.

### Is Lore production-ready?

Pre-stable 0.x release. APIs and protocols may evolve before 1.0 (when strict backward compatibility applies). Data written now is designed to remain readable by every future release.

### Does Lore support file locking?

Basic locking exists — users can place locks on non-mergeable assets to signal editing intent. **Enforcement is not yet in place** (informs rather than blocks). Next iteration focuses on cross-branch lock scalability for millions of files and thousands of concurrent users.

### How does Lore handle merge conflicts?

- **Text files**: Standard three-way merge.
- **Binary assets**: Conflicts surface as explicit divergence — user chooses which version to carry forward. File locking is the recommended workflow for binaries.

### How is Lore licensed?

MIT license. Fully open source, no restrictions or license fees.

### Is there a desktop client?

An early desktop client binary is available on the releases page. It is **not yet open source** (depends on some proprietary components including Epic's internal design system). Open-sourcing is committed for the future.

### Where is Lore already in use at Epic?

Lore (formerly **Unreal Revision Control**) is the built-in VCS for UEFN (Unreal Editor for Fortnite). Also seeing progressive adoption by internal Epic teams and being implemented as the backing store for UEFN's cook pipeline.

### How can I contribute?

All contributions welcome via GitHub. Uses **DCO (Developer Certificate of Origin)** rather than a CLA. Join the [Discord](https://discord.gg/E4SFJKRPbg). For significant changes (wire protocol, on-disk format, public APIs), use a **Lore Enhancement Proposal (LEP)**.

## Roadmap

### 2026 — Foundations

| Feature | Description |
|---------|-------------|
| **Lore OSS and UEFN compatibility** | Converge OSS and UEFN implementations. Key gap: UEFN uses Oodle compression, Lore uses Zstandard — actively moving UEFN to Zstandard. |
| **VS Code plugin** | Graphical interface in VS Code. Both plugin and source will be released as a complementary repository. |
| **Scalable file locking** | Scale locking to enforce single-editor access across millions of files and thousands of concurrent users. |
| **Virtual file system (VFS)** | Load files lazily as you open them, serving from Lore's shared store with fragment-level dedup. Eliminates up-front full clones. |
| **Links and layers** | Unlock multi-repository composition into a single working tree with per-repository access control. Data model already supports this. |

### 2027 — Scale and Collaboration

| Feature | Description |
|---------|-------------|
| **Desktop client** | Open-source the desktop client. |
| **Unreal Editor plugin** | Visual version control inside the Unreal Editor, built on the plugin that already ships with UEFN. |
| **Web client & code review tools** | Open-source browser-based home for code review, discussion, and repository management. |
| **Edge instances & advanced server topologies** | Server replication and caching for extreme distributed-team use cases. |

### Later — Exploring

| Feature | Description |
|---------|-------------|
| **Forks and isolated partitions** | Fork projects as independent, access-controlled copies that can merge back. Uses copy-on-write. |

### Governance

Evolving toward a **technical steering group** drawn from internal and external contributors, operating through public roadmaps, RFCs, and open meetings.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall