My agents were lying to me and I couldn't tell Retired NYPD detective. I run three businesses on Codex/Claude Code agents across three Macs. Last week I found out my monitoring layer had been reporting healthy while doing nothing, for months. Not broken. Lying. Different problem, and it's the one nobody talks about. Here's what a day of tearing it apart taught me, and the loop I built out of it. The failure nobody names Nine distinct ways my system reported success while failing. A few: - A wrapped job that exits 0 having done nothing gets reported GREEN. ~135 jobs affected. - A missing receipt is indistinguishable from a successful run. A job that never ran looks identical to one that passed. - Drop any `.json` file into a receipts directory and you fabricate a clean bill of health for 39 states. Worse — a stray file with a newer timestamp *displaces* a real failure record. I had a genuine timeout that got overwritten and turned green. - My alerting worked perfectly. It delivered six RED alerts over six days. Nobody read them. That last one matters most. The system wasn't blind. It was ignored. Alert fatigue is a design failure, not a discipline failure. Meanwhile a detector I'd built to catch exactly this had been running for ten days, correctly identifying that no leads had shipped to my ops manager — and telling nobody, because delivery was never armed. A working alarm wired to nothing. --- The loop Every agentic framework I read describes the same thing: an agent that generates, checks, and repeats. What none of them specify is what happens when the check says no. That's where mine lives. ``` ROUND N: 1. CONFIRM reproduce the defect behaviorally, never fix on description 2. FIX smallest diff at root cause, harden against the class 3. SELF-TEST builder proves it. Verdict here is PROVISIONAL. Always. 4. REGRESSION re-run every prior test, PLUS generate adversarial inputs against the surface this round just changed 5. AUDIT hand to a different model as an OPEN QUESTION —