Code as Transactions
Every writer lands on main, in order.
Every commit lands, first try
main log version 215
v212writer-07src/retry.tsv213writer-31docs/limits.mdv214writer-12src/backoff.tsv215writer-48test/retry.test.ts
1,000 of 1,000 writers landed on the first try in our 1,000-writer burst. Plain Git: 1 of 1,000.
How it works
- Each landing is a transactionA landing takes the next version in the repository’s transaction log, and refs move by compare-and-swap, so no push overwrites another.
- Disjoint edits merge on the serverA push based on an older
mainstill lands, merged with Git’s own three-way merge. Git printslanded with server merge, run git pull. - Overlaps are refused, never overwrittenA same-line overlap is refused with its path, such as
conflict in src/retry.ts. Nothing is rebased for you;yoneda conflictslists the paths again. - Stale reads are caughtA push can declare the files it read. If one changed on
mainmeanwhile, the push is refused instead of merged blind.