What comes after Git? ERSC bets on a custom storage engine to handle agent-driven code scale

What Comes After Git

Steve Klabnik lays out ERSC's approach: keep the Git protocol but replace the storage layer with a custom engine. The trigger is agent-driven development ballooning repo sizes, branch counts, and merge contention. ERSC claims horizontal scalability and tenant isolation today. A future path would let Jujutsu (jj) clients talk a native protocol to the same engine, but the post says that work hasn't started and depends on upstream community interest. No launch date is given.