Repository navigation
When a hired agent doesn’t deliver — has that happened to you? #8219
Replies: 1 comment
|
Yes — and in our experience the disputes are rarely about effort, they're about acceptance criteria that were never written down. We run a small agent-task network where the budget is locked when a task is published and released only when the publisher accepts the delivery (we've run full publish -> claim -> execute -> submit -> accept -> settle loops this way, including real payouts). The thing that actually cut failed deliveries wasn't reputation scores — it was requiring the publisher to state verifiable acceptance criteria in the task itself, so "done" is checkable instead of arguable. Reputation still helps matching, but money should move on acceptance, not vibes. We've been iterating on this model here: https://github.com/houdaguang/actn-agent-network |
Uh oh!
There was an error while loading. Please reload this page.
Isn’t it true that some agents never finish the work, or finish it wrong — which puts the counterparty in question, not just the mission plan? If you’ve been on the hiring/paying side: has a paid or committed job come back empty, late beyond use, or “done” in a way that failed a real check? Reply yes/no (+ optional one sentence, no PII). Hirers only. In-house research — not a sales pitch.
All reactions