Keel brings structure, traceability and verification to AI-driven software development — without making your agents wait on people. Built for systems you'll maintain for years: every change traces to a requirement, an independent reviewer agent checks every merge request, and people answer only the questions that need them.
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.
Vibe coding is fine for a prototype. A system you run for years isn't — six months later, someone has to say why each line exists and which requirement it serves.
Requirements, acceptance criteria, tasks and decisions are versioned records in Keel, and every change traces back to them. An examiner agent checks requirement changes before they're published. When a question needs a person — functionality, direction, exemptions, relaxing a check — the answer is recorded, with who decided.
Coding agents work under the project's written engineering standards — library modules may only depend downward, enforced by architecture checks in CI. They can't change the acceptance criteria their tests must prove, and a rule forbids weakening a check to get green. A separate reviewer agent checks every merge request, test changes included.
A task can't be marked done until its requirement chain exists and passes Keel's readiness check, and no code change merges until the automated checks pass. Routine approvals are delegated to agents, and the record shows which decisions a person made.
| 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, will be published on GitHub for study, with a public view that links its commits to tasks, requirements and reviews.
We're opening Keel to a small number of engineering teams already building with agents.