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.
機会をどう評価するか
Opportunity Scoreは測定値ではなく、私自身の見解です。どれほど痛みを伴うか、どれほど頻繁に影響を与えるか、そして今日時点で解決策がいかに少ないか。スコアが高いほど、構築する価値が高いと私は考えています。
それが現れたときにどれほどの痛みをもたらすか。
実際にどれほど頻繁に人々がそれに直面するか。
今日時点で、それに対する優れたツールがいかに少ないか。