Git

The dominant distributed version-control system — the incumbent that the spoke’s whole version-control corner is implicitly measured against. Git stores history as a graph of content-addressed objects (a Merkle structure keyed by hash), the same lineage lore invokes when it rebuilds VCS around “content-addressed Merkle storage” for large binary assets. Git is the baseline lore is reacting to (lore exists because Git “handles large binary assets poorly”), so paging Git gives that contrast its other half.

Where it sits in this spoke

• The version-control layer. Git is the general-purpose VCS for source + history; lore is the next-gen challenger on the large-asset axis, and monorepo scaling is in large part a Git-scaling problem (status, fetch, and repack costs grow with repo size).
• A third lever for “make the layer faster.” The spoke’s spine is the layer, not the lever: TS7 won speed by porting the compiler’s host language, V won memory by changing data layout, lore rethinks VCS storage. Git’s own answer is a fourth lever — incremental optimization of the established tool rather than a rewrite (see the git-2-55 release: filesystem monitoring, faster reachability bitmaps, incremental multi-pack indexing).

Scaling to large repositories — the live theme

Git’s large-repo performance is the practical face of the monorepo question. The 2.55 release is a concrete data point: FSMonitor on Linux (inotify) skips the full working-tree scan for git status; incremental multi-pack indexing and faster reachability-bitmap generation (one benchmark ~612s → ~294s) cut repack cost; path-walk improvements speed partial clones. These are the moves that keep a single huge repo — the monorepo’s core risk — usable, which is exactly the cost Block’s monorepo had to engineer around.

Geschichte takes a third stance toward Git (geschichte): not replace it (Lore) or tune it (2.55), but wrap it — read/write real Git objects while storing state in a Datalog database for queryable history.

Related

git-2-55 · lore · geschichte · monorepo · developer-tooling · block-monorepo-migration