WIPE_SCRIPTS

The Science of Engineering Incidents and Identity: Why It's Rarely the Villain's Fault

20 scripts this research explains — "Who broke prod?" feels like the right question after an outage. Systems research gives a less satisfying but far more u

“My name is attached to every failure, permanently.” Blameless-postmortem research is blunt: systems fail through conditions, not villains — but this script files every incident and every bug under your identity instead of the system's.

The Incident Ledger

“If nobody sees the work, the work — and I — don't count.” Invisible-labor research names the mechanic: well-maintained systems become infrastructure, and infrastructure is only noticed when it breaks. The script converts a measurement gap into a verdict on your worth.

The Invisible Infra Script

“If my output can be replaced or discarded, so can I.” Survey data says otherwise: 84% of developers use AI tools, yet 46% distrust the output and most don't see them as a job threat — judgment and verification are the job. This script compiles every replaced artifact into a replaced self.

The Obsolescence Compiler

"I inherited this mess, so every flaw is mine to fix immediately." Anchoring-bias research shows developers unconsciously lower their standards when taking over poorly-maintained systems, rationalizing "it's legacy, no place for clean code here." This script transforms inherited debt into personal debt—every preexisting flaw becomes evidence you should have known the full context the moment you took it over.

The Legacy Inheritance Script

View full research file ↗All wipe scripts