Recursive Harness Engineering
Harness engineering first, then recursive improvement.
Production AI systems · Berlin
I design production AI systems across software engineering, agents, evaluation, retrieval, security, and infrastructure—turning traces and failures into controlled experiments, reliable releases, and safer behavior.
My Recursive Harness Engineering series starts with the foundations: build a harness, evaluate its behavior independently, and test changes. Later chapters will automate the search for improvements and investigate whether experience from earlier rounds helps on new tasks.
Automate the experiment, not the authority to declare it safe.
Harness engineering first, then recursive improvement.
In order. Start at the loop.
Most read
The same support tasks as an agent, an agent with approval, an agent in a workflow, a router and a workflow with no agent, compared on one test set.
How task requirements shape an agent harness: choosing control flow, tools, code execution, state, permissions and evidence before choosing a framework.
A prologue to recursive harness engineering: test an LLM's sequential changes to a memory tool, then check whether simple search finds the same result.
About
I’m Slava Dubrov, a Staff AI System Engineer with a doctoral degree in AI diagnostics. I work across software engineering, agent systems, evaluation, retrieval, security, and production infrastructure.