Field Notes from the Rescue Bench
What we learn hardening vibe-coded and AI-generated apps for production, published as we learn it.
-
Sample Rescue Audit: A Vibe-Coded ERP
A real audit, redacted: RLS enabled on every table and still wide open, the tests nobody runs, and why one scanner said the sky was falling while another said everything was fine.
-
Vibe-Code Rescue: What It Is and When You Need It
Rescue, a rewrite, an agency, a freelancer, a new hire, or waiting: which fix a breaking AI-built app actually needs, and the audit-first shape of the one we run.
-
Should You Rewrite Your Vibe-Coded App? Almost Never.
Why code that works in production is an asset no rewrite has, the decision rule we use, and the three narrow cases where starting over wins.
-
How to Harden an AI-Generated Codebase (Without Stopping Feature Work)
The priority order that works: error tracking, money-path tests, a CI ratchet, authorization, constraints. Hardening runs alongside shipping, not instead of it.
-
What Breaks First When a Vibe-Coded App Meets Real Users
The failure sequence we keep seeing once real traffic arrives: authorization edges, webhooks, data integrity, silent errors, and what hardening actually means.