https://t0ul.com/tags/durability/Recent content in Durability on t0ulHugoen-usTue, 01 Sep 2026 00:00:00 +0000https://t0ul.com/blog/durable-execution-and-resume-verify/Tue, 01 Sep 2026 00:00:00 +0000https://t0ul.com/blog/durable-execution-and-resume-verify/<p><em>Part of my <a href="https://t0ul.com/blog/the-plan/">AI Security Engineering</a> series, a local email-to-calendar agent I build, then attack, then harden. If you have not set up the lab yet, start with <a href="https://t0ul.com/blog/setting-up-the-lab/">Set up your lab</a>. The lessons are <a href="https://github.com/t0ul/ai-security-engineering">on GitHub</a>, and the agent itself lives at <a href="https://github.com/t0ul/emaildrop">t0ul/emaildrop</a>.</em></p> <h2 id="crashes-are-not-attacks-until-they-are">Crashes are not attacks, until they are</h2> <p>The last part governed the agent. This one makes it survive the boring disasters: a crash mid-task, a retry after a timeout, a context window that fills up. These are not attacks, they are the ordinary physics of running software, and the reason they belong in a security book is that the mechanisms you add to survive them become attack surface of their own. A system that can resume is a system that trusts something it wrote down earlier, and anything the agent trusts is worth examining.</p>