# A green suite that never ran is not evidence > Source: > Published: 2026-09-11 16:01:10+00:00 I have spent a stretch of weeks on a live system where the dangerous part was not a crash. It was quiet. A provenance log that had written zero bytes for months. Tests that scored green without executing. A veto that had been dropping valid setups while the board still looked calm. A calendar built for the wrong exchange. None of that announces itself. The UI still loads. The agent still reports progress. Someone still says the suite is green. I direct AI coding agents on work like this. Multi-week rewires. Typed contracts. Shadow paths. The agent is fast. The agent will also tell you a push landed when you have not checked the remote, or that a cost number is solid when it was inferred from a fixture. I treat the report as a claim. Then I check the claim. The practice I now keep is small. Every negative result needs a positive control. If the test says nothing happened, I need proof the test can detect a real break. Mutation first. Break the thing the fix is supposed to catch. Confirm the suite sees it. Restore. Distinguish measurement from inference. An extraction bug is not a market finding. A time zone error is not a data gap. Write the correction down before it becomes folklore. On a live rewire, keep the old path authoritative until the new path is proven in shadow. One boundary at a time. Do not cut over on confidence. If you are using an agent on a system that already carries money, records, or a book, the skill is not the prompt. The skill is knowing what to re-run yourself. I do this work at Meraki is Love. Studio site: merakislove.com