The harness of harnesses
deadreckon does not replace your coding agent — it wraps the agent CLI you already trust and supervises the loop around it.
maps to as-built §1
deadreckon is not another coding agent. It is the layer around the coding agent you already use. The agent does the thinking and the typing; deadreckon owns the loop (running the agent over and over until the work passes its checks), the isolation, and the decision about when the work is actually finished.
That is why the picture nests. Your agent CLI is already a harness: it wraps a model and feeds it tools. deadreckon wraps that, adding the parts a single agent session can't give you on its own: a run that survives a closed laptop, a checkout that never gets touched, and a finish line the agent cannot move on its own.