Menu

Why the model shouldn't be the one that says "done"
📰

Why the model shouldn't be the one that says "done"

DEV Community: rust·Vaibhav·5 days ago
#dIDoPTMj
#devtorust#devto#dev#loopsmith#work
Reading 0:00
15s threshold

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 agent finishes, says "done", and I open the output to find a missing section, a citation that points nowhere, or a test it quietly edited so it would pass.

So I built a small tool around one rule. The model never gets to say "done". I call it loopsmith : a skill that creates self-evolving, loop-based, purpose-specific skills, backed by a Rust CLI. It's MIT-licensed, at v1.0.0, and I'm sharing it here to find out whether the idea holds up for other people.

20-second demo: watch it with sound .

The problem with self-certified completion

Most agent loops end in one of two ways.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.