> In some cases, the new AI workflow may even destroy value.

I am really struggling with this one right now.

The client's development team is letting Claude document and refactor the product codebase without much intervention, purpose or taste. The thinking being that if Claude first writes a bunch of unit tests and then a bunch of documentation, that any downstream refactoring will magically work out.

I don't know how to convey to management how stupid this is without allowing it to fail in production. AI psychosis (or whatever we want to call it) being a new phenomenon means we might as well be speaking in moon runes to the CEO when trying to explain the situation.

The best countermeasure I can come up with right now is to use their momentum against them. Accelerate the failure. I've got the last known good commit hash written down on a sticky note on my monitor.