Glossary · Building the harness
Agent harness
Also called harness.
An agent harness is everything around the model that makes unattended work safe: the schedules that start it, the credentials it never sees, the guards that stop it acting twice, and the state that survives a crash mid-job.
What we can add
Our position is that the harness, not the model, is the product — and the specific consequence we act on is that coordination state belongs in the database. If a run can suspend for days waiting on a client, everything needed to resume it has to outlive a deploy, a crash and a second replica, which rules out holding it in memory however convenient that is.
Go deeper