Most durable execution systems recover by replaying retained execution history. After a worker fails, a fresh worker loads the history and re-executes the program until it reconstructs the current position. This is a useful model. It provides durable progress while allowing workers to remain ephemeral. But it also makes accumulated history part of the recovery path. That tradeoff becomes more noticeable for programs that operate for hours or days, call many tools, wait for external events, creat...