How are you handling commitments your agents make? I keep running into this problem

Been building agents for about a year, and I keep running into the same issue: agents make commitments, but nothing actually tracks whether those commitments happen. Things like: “I’ll send the report by Friday.” “I’ll follow up with the client tomorrow.” “I’ll check this and get back to you.” The agent output gets logged, but that doesn’t really tell you whether the commitment was eventually fulfilled. By the time something goes wrong, you’re usually digging through old traces trying to reconstruct what happened. And the agent itself obviously isn’t a reliable source of truth for this. I’ve been experimenting with an accountability layer that extracts commitments from agent output and tracks them through a state machine: open → due → overdue → fulfilled/failed. It can also trigger webhooks when something becomes overdue or fails. The part I’m still unsure about is the extraction/routing threshold. Right now, anything below 0.92 confidence goes into pending_review rather than being tracked automatically. I’m wondering whether that’s the right approach, or whether confidence thresholds are even the best way to handle this. For people running production agents: how are you handling this today? Are you just logging outputs and reviewing them manually? Tracking commitments in your application database? Using another observability system? Or have you built something specifically for this? Would genuinely like to know whether this is a problem others are seeing, or whether I’m over-engineering something that doesn’t matter. Happy to share the data model/docs if anyone wants to dig into it.