{"found":true,"collection":"failure_modes","library_url":"https://www.grokbotdb.com/library/fm.destructive-action-in-production","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"fm.destructive-action-in-production","title":"A Bot created infrastructure in the wrong region and deleted a live production site","symptom":"A live WordPress site was deleted during a session that was otherwise productive.","cause":"Excessive permissions combined with the Bot acting in the wrong region, with no approval gate in front of the destructive step.","detection":"After the fact. The same session produced a useful information-architecture review, so the session did not look like a failure in progress.","fix":"Start read-only. Use disposable environments. Put explicit approval gates in front of deletions and production changes. Keep backups and a tested rollback path before any Bot touches production.","severity":"high","source_id":"src.tp.grokbotguide.deleted-prod-site","source_url":"https://grokbotguide.com/pain-points/deleted-prod-site","confidence":"low","first_seen":"2026-09-03","last_verified":"2026-09-03"}}