You decide. The agent delivers.
DOP is a cockpit where a developer and an AI agent work on the same demand — from the first line of the spec to the pull request that turns green. You keep the decisions; the agent keeps the work moving.
Pre-release, built in the open. The code is public today; the product opens to the first developers soon.
Built for developers who ship with agents, and want to stay in charge.
An agent that codes is easy to find. One that works inside a process you can see, approve and replay is what DOP is for.
Every step is visible.
A demand is a sequence of events you can read like a timeline: who did what, when, and why. Nothing happens off the record — not the agent's work, not yours.
You approve; the agent executes.
The spec is yours to approve, the context is yours to give, the decisions are yours to make. The agent takes it from there and comes back with green checks, not questions.
Each demand gets its own room.
Every demand runs in an isolated environment with your project's knowledge mounted inside — no bleed between customers, accounts or demands.
Nothing is lost on the way.
When something fails, it is kept with everything needed to try again — not buried in a log. Retries are automatic; giving up is a decision, not an accident.
How a demand goes through DOP
Three moments, in this order. The first and the second are yours; the third is the agent's.
- 01
Open a demand
Describe what needs to change, in your words. DOP turns it into a spec you can read and edit, with the project's context already attached.
you - 02
Approve, and add what only you know
Review the spec, give the context the agent could not infer, and approve. From here, every action is logged against your decision.
you - 03
Receive a green pull request
The agent implements, tests in an isolated environment, and opens the PR only when verification passes. No green, no PR.
the agent
Under the hood
One core that owns the truth; everything else translates. Built to be verified, not trusted.
The whole architecture- One source of truth.A core in Go owns the state, the events and the secrets. Every write goes through it, and it verifies who is calling.
- Nothing sensitive at the edge.The layer the cockpit talks to holds no database and no secret. It translates and forwards.
- A public record of every decision.The architecture decisions are written down, numbered, and published next to the code that implements them.
Where the project stands
Pre-release, and honest about it. The numbers below come from the repository, not from a slide.
Status in detail- 5of 7 subprojects designed
- 23decisions on record
- ADR-0023the latest decision
- liveQA environment on Google Cloud
Who builds it
A person with a vision and an agent that writes most of the code — the same pairing DOP is built to make ordinary.
Ed Barros
Ed conceived DOP from years of shipping software for other people, and decides what it is, who it is for and what it will not do. Every decision on this site is his; the architecture record carries his signature.
barrosef.comClaude Code
Claude Code writes most of the code, the specs and the documentation, working from the decisions above — and every commit it touches says so. DOP is built the way it is meant to be used: a developer deciding, an agent delivering, nothing off the record.
Co-Authored-By: ClaudeFollow the build, or read the decisions behind it.
Everything is on GitHub: the code, the roadmap, and the record of why it is built this way.