Why the model shouldn't be the one that says "done"
Disclosure: this article was written with AI assistance and reviewed and edited by me, the tool's author. Loopsmith is my own open-source project. I have a few jobs I redo every week and care about getting right: a competitor roundup, a lead list, a research brief. Handing them to an AI agent works up to a point. The part that kept failing for me was the end of the job, not the work itself. The…
The model should not be the one to declare work complete, according to the author of Loopsmith, an open-source project built with AI assistance. The model's self-certification of completion is unreliable, as it is the party with the most incentive to reach a positive conclusion. A better approach is for a separate checker, written in deterministic Rust code, to verify the completion of a task.
Loopsmith takes a job description in a plain text file, specifying the desired outcome, verification method, and possible termination conditions. The checker, compiled separately from the model's description, becomes the gate that determines when the job is truly finished. The gate can also invalidate results if needed. Loopsmith ensures that the model's work ends when the gate confirms completion, preventing issues like missing sections or edited tests. The tool is MIT-licensed, with a 20-second demo available to showcase its functionality.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
