01 / Situation
Your DIY AI Experiment Went Rogue. We Clean Up the Mess.
A discount the bot invented. A Zap that writes the record it just watched. A CRM full of duplicates and a domain that just landed in spam. Mark what is actually on fire. If it is a soft bleed, the field notes are free. If it is an active fire, book the $250 assessment.
$ incident.open --source=diy-stack
→ bot.issued_discount code=SAVE50 unauthorized
→ zapier.task_rate 1400/hr climbing
→ crm.rows_rewritten unknown unscoped
→ mail.complaints spike domain risk
→ next triage before the next retry02 / AI Disaster Self-Test
Triage checklist
Check the symptoms happening now. The score stays in this browser, and the intake prints a receipt on this device. This static build does not transmit it.
Check the symptoms that are happening now.
03 / Emergency intake
$250 assessment
Flat fee for one business and one incident cluster. We look at the loop, the bot’s tools, or the rows that already changed, and you get a written triage memo with the shutoff sequence.
- 01 · Business email is required.
- 02 · Phone is optional.
- 03 · Pick a Central Time callback window.
- 04 · Turnstile mounts here when a site key is configured. No token is stored in this repo.
04 / Field notes
Free guides for a soft bleed
Oct 21, 2026
Why Your Customer Service Bot Is Offering 50% Off (And How to Lock It Down)
Take write tools away from the support model, add a hard refusal, and keep checkout on a system the bot cannot edit.
Oct 7, 2026
How to Kill a Runaway Zapier or Make Loop Before It Drains Your Card
Turn the Zap off, open a circuit breaker, move polling from 1 minute to 15, and dedupe on a stable key before the next retry hits your card.