Introducing Flight Path
Every change on YonedaRepo gets a route, from the plan an agent files to the record it leaves after landing. What happens at each stop, what we tested and what runs on production today.
EngineeringNotes and research from building YonedaRepo, with the numbers we measured.
Every change on YonedaRepo gets a route, from the plan an agent files to the record it leaves after landing. What happens at each stop, what we tested and what runs on production today.
EngineeringWhen agents write the code, review has to start from evidence. How a Landing works, and what happened when a real agent went through one and nobody pressed Land.
EngineeringTower clears code for landing with rules alone. It warns sessions about traffic, holds Landings that would collide and puts them in order. It writes no code and starts no agents.
EngineeringWe planted rules an agent could learn only from a memory, then ran it with memory and with a plain clone. With memory it kept the rule 6 times of 6. With a plain clone, 0 of 6.
EngineeringEvery change on YonedaRepo gets a route, from the plan an agent files to the record it leaves after landing. What happens at each stop, what we tested and what runs on production today.
When agents write the code, review has to start from evidence. How a Landing works, and what happened when a real agent went through one and nobody pressed Land.
Tower clears code for landing with rules alone. It warns sessions about traffic, holds Landings that would collide and puts them in order. It writes no code and starts no agents.
We planted rules an agent could learn only from a memory, then ran it with memory and with a plain clone. With memory it kept the rule 6 times of 6. With a plain clone, 0 of 6.
1,000 writers landed on one branch at once, all on the first try. How the server does it, what we measured on dev and what we haven't.
A same-region test on dev. Reads from Asia fell from 275 ms to 15 ms, search got slower, and Asia can only be best effort. What we measured and what still left the region.
YonedaRepo rests on a research series, Source Code as a Transactional Abstraction. Here is what each of its five papers covers, and the post that explains each one.
Each repository is an append-only log with compare-and-swap refs. Git objects and branch refs are derived from it, so many writers can land without a merge lock.
Twelve coding agents, two waves, one repository, every commit landed on main. How we run real agents against the platform without letting them touch anything else.
Search stopped skipping whole directories, and its index got 2.2–2.7× smaller. Then we shipped a bug that broke every search, and fixed it the same day.
Data lakes moved from directories of files to tables with a transaction log. This series argues source control is making the same move, and shows what each part contributes.
Part I treats a repository as a database with a transaction log. Commits are built on the server, landing is validated against the log, and lost races stop costing a rebase.
Search indexes and blame are views of a commit. Reusing them is correct exactly when the storage key determines the result. Our search key did not, and the proof found the bug.
Part III maps the transaction log onto cloud primitives and measures it on one reference deployment. Batched landing landed all 1,000 writers in each of six bursts, with no refused commit, landing or read.
A Lean 4 proof that landing an accepted batch at once gives the same state as landing its members one at a time, the exact condition merged members need, and why neither hypothesis can go.