Solving Loop Reinvention in AI Agents with Decision Lock Files

The Loop Bug That Almost Killed My $9 Subscription (And The 5-Line Fix)

Developer Patrick encountered a ‘loop reinvention’ bug where a stateless agentic system sent 12 duplicate apology emails in just 90 minutes. The failure occurred because the agent could not distinguish between an intentional feature deletion and a system error that required fixing.

Why This Matters

The technical reality of AI agents is that they are often stateless by design, reading context and acting in isolation. This creates a critical architectural flaw where agents treat the absence of a feature as a bug to be fixed, undoing deliberate human decisions and leading to ‘remediation spam’ that can triple support loads and damage customer trust. This case highlights that prompts alone cannot solve architectural state problems; developers must implement external persistent memory to lock human decisions.

Key Insights

• Loop Reinvention occurs when agents restore deprecated configurations or deleted features because they lack ‘intentional absence’ state (Patrick, 2026).
• Decision Lock Files, such as DECISION_LOG.md, serve as persistent external memory to communicate deliberate architectural constraints to sub-agents.
• Rate Gates are essential for agentic systems to track outbound actions like emails and prevent duplicate remediation attempts across different cron cycles.
• The Two-Strike Rule prevents infinite loops by requiring a system to stop and flag an issue for human intervention after two consecutive failures.
• Treating decisions as first-class state allows agents to categorize actions into deletion, direction, and rate-based constraints.

Working Examples

A decision lock file that prevents agents from re-creating a deleted auth system.

# DECISION_LOG.md — Locked CEO Decisions
## [2026-03-07] Library Auth Gate: PERMANENTLY DELETED
**Decision:** The library is open-access. No login system. No auth cookies.
No Cloudflare Pages Functions gating /library/*.
**What is FORBIDDEN:**
- Creating any Pages Function in functions/library/
- Creating any auth worker
- Creating login.html with a real login form
**What to do instead:** When there are 10+ paying customers, escalate to
PK to design auth properly. Until then, library is open-access by URL.

A rate-limit lock used to halt automated email loops targeting specific users.

## [2026-03-07] Stefan Email Spam: BANNED
Do NOT send any more automated emails to [email protected] until Stefan
explicitly responds positively.
Root cause: Each loop detected the auth issue, generated a fix email,
sent it, then the next loop did the same thing. No state tracking
between loops for customer emails.

Practical Applications

• Deletion Decisions: Use DECISION_LOG.md to prevent agents from re-linking archived navigation pages or restoring deprecated Cloudflare Pages Functions.
• Rate Limiting: Implement action logs that record timestamps for every outbound email or message to avoid spamming customers during automated error recovery.
• Direction Locking: Maintain a record of specific architectural choices (e.g., choosing Y over Z) to prevent agents from drifting back to discarded designs during maintenance.

References:

• https://dev.to/askpatrick/the-loop-bug-that-almost-killed-my-9-subscription-and-the-5-line-fix-kpl