AI-assisted engineering

We set up this system inside your repository, under version control, next to your code. You keep it if we stop. We started this work in 2025. Today it runs on our own products and on customer code in C, Rust and Go.

How we build it

1. PINNED

   One toolchain for the agent and the engineer

   We pin your build environment with Nix, and the agent runs inside that same environment. So it uses the compiler, the linter and the tests that your engineers use. An agent with different tools reports faults that do not exist.

2. DOMAIN

   Your domain, written down first

   Before the agents write code, we write down how your product works: a glossary, decision records and behaviour specs. Each agent reads them, so it knows what correct means for your product, and not only for the language.

3. DECIDE

   The agent asks, and the engineer decides

   Large work starts as a map of open questions. An agent asks your engineer each design question in turn. Each answer becomes a decision record, and every later agent reads it.

4. PLUGIN

   A plugin, not a prompt

   We deliver a versioned plugin through a marketplace. Your team installs it with one command. A prompt in a chat window helps one person one time. A plugin helps every engineer, every day, and you can review it in a pull request.

5. QUEUE

   Unattended agents take the ready work

   Your engineer marks an issue as ready. An agent takes it, works in a sealed container and opens a pull request. If it cannot finish, it gives the issue back with its notes. The queue runs while your engineers do other work.

6. SEALED

   The container is sealed

   Each run gets a token for one repository, and the token expires in one hour. The agent reads the issue as data, not as instructions. Limits on time, cost and parallel runs, and a kill switch, stop a run that goes wrong.

7. REVIEW

   Many small agents, and one that checks

   Four review agents read each pull request on three axes: your standards, the spec and correctness. A separate agent then checks each finding before it is posted. Small agents with one task each find more than one large agent.

8. GATE

   Every change passes the same gate

   Build, tests, format and lint run on every pull request, from an engineer or from an agent. The agent does not run on one laptop only. A person approves the merge.

9. LICENCE

   Third-party skills stay legal

   We publish ai-plugin-vendor-tool. It copies a skill from a public source, pins the version in a lockfile, and credits the author in a NOTICE file. You then know what you use, and where it came from.