
Chris Dudek
Software engineer. I build with AI agents and prove their work.
What I do for engineering teams
I build the verification layer that lets teams deliver with coding agents without giving up their standards: harness setup on your repositories, quality gates and architecture checks the agent can't skip, team enablement, and AI-assisted delivery of production applications. B2B contracts.
me@chrisdudek.com →Jarl is the loop. Yggdrasil is the law. Grain is the survey. Horde runs a mission on all three. The four ship under one version number; start with the one that fixes what hurts.
The loop. Every finding becomes an issue, each issue gets one worker in its own worktree, and nothing closes without evidence and a fresh reviewer's word. Where your repository has a check, the check decides what lands.
The law. Say it once: a rule you write holds in every session after, and the agent has to satisfy it before it moves on. Free local checks, keyless CI.
The survey. Point it at a repository nobody has annotated and it writes the first architecture graph from the code and the history, each rule with the count of places that break it today. It earns its keep the moment you are about to write law.
The mission on the law. A one-shot architect plans the whole mission onto Yggdrasil's graph, measuring with Grain; a worker per ticket; every change lands through a gate no agent can argue with. It runs on Jarl's loop, and you are the client who can veto any rule it raises.
Add-ons
A translator between you and your codebase, so you follow what it's doing in plain words, not code.
Consults the source of truth and asks instead of guessing.
One file that turns a coding agent into an experimenter: hypotheses kept and discarded, 30+ experiments overnight. 250+ GitHub stars.
Films of your real running software, made by your coding agent. Every number and claim on screen traces back to the product's own logs.
© 2026 Chris Dudek