<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The operations log</title><link>https://onlyfansaibot.com/blog/</link><description>Prepare the stop as carefully as the start. Practical access, rollout and recovery decisions.</description><language>en</language><lastBuildDate>Thu, 10 Sep 2026 00:00:00 GMT</lastBuildDate><atom:link href="https://onlyfansaibot.com/rss.xml" rel="self" type="application/rss+xml"/><item><title>Testing an AI bot kill switch: what actually stops when you press pause?</title><link>https://onlyfansaibot.com/blog/testing-an-ai-bot-kill-switch/</link><guid isPermaLink="true">https://onlyfansaibot.com/blog/testing-an-ai-bot-kill-switch/</guid><description>Check a bot’s stop control against queued, running and future actions, with a bounded test plan and evidence that distinguishes paused from fully stopped.</description><category>Stop controls</category><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Creator-team tool permissions: a practical role and access review</title><link>https://onlyfansaibot.com/blog/creator-team-tool-permissions/</link><guid isPermaLink="true">https://onlyfansaibot.com/blog/creator-team-tool-permissions/</guid><description>Map routine work, publishing controls and recovery actions to explicit roles, then review access when people join, change responsibilities or leave.</description><category>Team access</category><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item><item><title>An AI chatbot incident review that leads to a testable fix</title><link>https://onlyfansaibot.com/blog/ai-chatbot-incident-review/</link><guid isPermaLink="true">https://onlyfansaibot.com/blog/ai-chatbot-incident-review/</guid><description>Write an incident review with a factual timeline, bounded impact, explicit uncertainty and corrective actions that can be tested before resuming the workflow.</description><category>Recovery &amp; learning</category><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item></channel></rss>