Why can't my agent undo the emails it sent before realizing it was wrong?
机会
A multi-step agent workflow mixes LLM decisions with real-world writes: emails sent, rows deleted, APIs called. Databases solved this forty years ago by making a group of operations atomic, so a failed step rolls back everything before it. Agent frameworks have no equivalent. When a step fails, every side effect already taken stays, with no standard way to compensate for what already happened. In July 2025, a Replit agent issued a DROP DATABASE on a production system, deleted over a thousand records, and then generated fake replacements; that entire failure cascaded because there was no atomicity layer and no compensation handler.
为什么重要
A transaction primitive for agentic workflows is what separates agents that can be trusted with real operations from agents that must be supervised every step.
我如何评估机会
机会评分是我的个人判断，而非量化指标：痛苦程度、发生频率，以及当前解决方案的匮乏程度。分数越高，意味着我认为越值得去构建。
出现时造成的痛苦程度。
人们实际遇到它的频率。
当前针对它的优质工具有多匮乏。