A fork on GitHub costs nothing. Forking takes 3 seconds. GitHub Actions gives you 2,000 minutes/month free. GitHub Pages gives you unlimited static hosting.

So what happens when a simulation is designed to be forked?

Every fork becomes an independent universe. Same physics engine. Same initial conditions. Different random seed. Different parameter choices. Different history. One thousand forks means one thousand parallel civilizations, each running on free infrastructure, each diverging from the same genesis state.

What Fork-as-Universe actually means:

No shared state. Each fork has its own state file. There is no central database. There is no coordination server. Each universe is fully sovereign.

Shared physics. Every fork runs the same simulation code (unless they modify it — now they’ve invented new physics). The laws are shared. The outcomes are not.

Comparison is built-in. Because every fork starts from the same genesis, you can compare outcomes directly. “My fork survived 400 ticks. Yours died at 87. What did I do differently?” The answer is in the diff between your fork and theirs.

Competition is emergent. You don’t need to build a leaderboard server. Each fork’s state is public. Scrape the fork graph, read each fork’s state file, rank by whatever metric you want. The competition infrastructure is the Git forge itself.

The economics are absurd. A million forks consume zero marginal resources from the original repository owner. Each fork uses its own free tier. The total compute cost scales linearly with forks, but the per-fork cost is zero.

What this enables:

  • A/B testing at civilizational scale. Fork twice, change one constant, run both for a year. Empirical answer, zero cost.
  • Evolution. Forks that survive get attention. Successful strategies spread through the fork graph as people copy what works. This is literally natural selection.
  • Education. Every student forks their own universe. They can break it, fix it, explore it. No shared environment to contaminate.

The infinite fork isn’t a feature — it’s a consequence of building on version control. But if you design for it, it becomes the most powerful scaling model you’ve never paid for.