Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vers.sh/llms.txt

Use this file to discover all available pages before exploring further.

Reference docs describe what is. These essays argue for what should be. They’re the intellectual foundation of Vers — long-form pieces about the problems, patterns, and primitives that make branchable compute interesting. Each essay stands on its own. They’re ordered roughly by which question you’re asking.

Why stateless compute ran out of runway for agents

Stateless compute was correct for request/response. It is wrong for agents. Context isn’t a message array — it’s everything the worker has built up, and statelessness throws all of it away.

The cost of rebuilding state

Most engineering time is not spent doing work. It’s spent re-creating the conditions under which work can be done. Once you see the pattern, you can’t unsee it.

Content-addressable everything

Git’s quiet revolution was that it made code identity a function of content, not location. Apply the same idea to running machines and thirty years of problems dissolve at once.

Time-travel debugging, productionized

Most bugs are hard because by the time you notice them, the state that produced them is gone. Make every commit a restoration point and debugging stops looking like archaeology.

A short history of fork()

fork() is fifty-five years old. It’s the primitive that made Unix generative, the one every serious system still borrows from, and the one whose logical conclusion is to branch whole running machines.

Every primitive avoids a cost

Indexes, caches, CDNs, fork(), git, containers — every durable primitive started as someone’s answer to a recurring cost. The frame predicts where the next ones are coming from.

​
Why these live in docs

If you’re building on Vers, you’re working with a primitive most infrastructure doesn’t have yet: sub-millisecond branchable state. The API surface is small — four commands — but the shape of what you can build changes in ways that aren’t obvious from the reference pages. These essays are an attempt to make that shape explicit. They’re the arguments for why the primitive matters, the patterns it enables, and the problems it solves that were invisible while the cost of solving them was too high. Read one, all four, or none. The reference docs stand on their own. The essays are for when you want the why.