Blog
Field notes
How a described business becomes software you can run — and why some of it never launches. The older notes get technical. The rule is the same.
When the proof gate met Solidity
We pointed the same proof discipline at smart contracts — and found we could do better than runtime testing. Symbolic execution that proves a property over every input, certificates bound to the deployed bytecode, and a hard line on what we refuse to claim.
Read post →Two cents a build: the economics of proof
Zeta writes one spec at ~3,000 tokens/sec, then proves the whole app deterministically. The proving is free. Here's what a verified full-stack app actually costs to run — measured across 236 real builds.
Proof, not vibes: where ISL is headed
What we discovered building ISL — a domain spec language that compiles one prompt into an app whose safety is adversarially proven against a real database — and the roadmap from here.
The pipeline is real
One window of work. Ten agents in isolated worktrees. Twenty commits on main and ~320 green tests proving that natural language → cryptographically verified TypeScript is no longer a slide deck.
The bet behind ISL
A year building a specification language for AI code. Natural language is the drift, not the interface — here's the thesis, what already ships, and what comes next.
Can we actually ship safe AI code?
A night with the gate, Intent Specification, and the wall ahead — cloning real Next.js repos, hand-writing OAuth specs, reading 50MB of bundled CLI, and asking the question the vibe-coding decks won't answer.
The origins of ISL
From VibeCheck's truthpack to a compiler contract: why AI-generated code needs an executable intent contract, and how ISL came to be.