Proof, delivery, and agents.
Engineering notes on making autonomous software delivery faster without making trust implicit.
The failure that costs you is the one that gets into the merge queue
We merge about 190 pull requests a day, most of them written by coding agents, on a small-company budget. What changed was deciding what is allowed into the merge queue.
Why not just use a Git hook?
It is the question we hear most. A hook is the right tool when you trust whoever is pushing. When the pusher is a coding agent, the check has to run where the agent cannot skip it.
Agents broke CI. Here is the part you can fix today.
Anthropic replaced git for its monorepo because agents outran source control, builds, and CI. Most teams will never do that. They can stop waiting on a shared CI queue to learn whether a check passed.
Trace a test before you trust its cache hit
Use a local CI/lock trace to inspect test behavior, then prove that a relevant input change invalidates the cached result.
Introducing Pushgate: proof before code lands
Pushgate is an evidence gate for agent-written code: CI/lock produces commit-bound proof, and Pushgate checks it before forwarding a Git push.