Your agents write more code than your team can review. Keel traces every change to a requirement, has an independent reviewer agent check every merge request — test changes included — and keeps people in charge of direction.
Agents produce more code than people can read. Review becomes the bottleneck — or a rubber stamp.
Code that compiles and passes its own tests — but does something nobody asked for.
An agent that writes the code, the tests and the definition of done will always pass its own exam.
Six months later, nobody can say why a line exists or which requirement it serves.
A separate reviewer agent checks every merge request, including any change to tests — never the agent that wrote it. The coding agent can't change the acceptance criteria its tests must prove, and a rule forbids weakening a check to get green.
Requirement → acceptance criteria → test → review → merge, each a versioned record. An examiner agent checks requirement changes before they're published, and a task can't be marked done until its requirement chain passes Keel's readiness check.
Questions about functionality, direction, exemptions or relaxing a check go to a person, and agents record the answer verbatim. Routine approvals are delegated — and the record shows which is which.
| People decide | Agents do |
|---|---|
| What to build, and in what order | Draft and evaluate requirements |
| How a feature should behave, when asked | Design test scenarios and cases |
| Exemptions and relaxed checks | Write the code and the unit tests |
| Credentials and access | Review each other's work, merge, release |
Keel is developed under its own governance. DynoInvoice, an invoicing system built with Keel, is being published on GitHub, with every commit traceable on dynokore.dev.
We're opening Keel to a small number of engineering teams already building with agents.