Software writes
itself now.
The open engine for autonomous software production.
Release notes, essays, and new engine drops: no noise, only when a layer ships.
The engine · shipping in the open
Two layers out. Three to build.
The engine is layered because trust is layered. Each layer is extracted from the platform we run, then opened: starting with verification, now constraints.
Self-driving software engineering.
The agent that wrote the code shouldn't be the one that says it works. Bring your own model, provider, and stack.
A deterministic, local, read-only validation gate for coding agents. Coverage before findings, then one verdict an agent can act on. Every change, within tolerance.
Verification · Zeroshot
A validation loop kept independent from the intelligence that produced the work. The layer that survives real use, shipped first.
Three layers still being built
Watch the engine
get built.
No noise. Only when a layer ships. One email per layer, nothing else.
Why us
We run the apparatus we sell.
Zeroshot (verification) and Opcore (constraints) are open-source and run today. The verifier stays independent from the model that wrote the code, and the gate keeps every change within what the codebase can actually hold, so a pass, and a CLEARED, mean something. Bring your own model, provider, cloud, and database. Every layer ships the same way: extracted from the platform we run, then opened.
Why now
Generating code is easy. Trusting it is not.
Writing code is no longer the constraint; reviewing and trusting machine-written code is. The tools that close that gap, verification, constraints, context, are being built across the industry right now. Built proprietary, they become a dependency you cannot leave. Built open, they stay yours.
The charter
Read the full charterWhy software production changed, and why its infrastructure must stay open. In four articles.