It started with a routine task, as it usually does. I was using Claude to review a draft critique of an article I had some doubts about, checking the research behind a few of its assertions and testing its logic.

During the exchange, I noticed something simple: Claude was applying a strict standard of proof

People seem to like my AI session transcripts where I see big AI failures. I definitely don’t like living through them, but they can be instructive to readers of this blog.

Here’s an excerpt that will give you much to think about. Note my prompting style (my two prompts are in bold) as we reached

In the latest episode of The Kennedy-Mighell Report, Tom Mighell and I turned the spotlight inward to talk about the course I just finished teaching at the University of Michigan Law School called Legal Technology Literacy and Leadership. This course is considered a practical simulation class. It was built this past semester around

When I started posting about AI this year, I did not realize that I was beginning my own version of David Bowie’s Low album.

I use that comparison carefully. Low matters here not as a code book or a track-by-track template, but as an allusion to emergence, fracture, atmosphere, and a break in method that

There are moments in a long AI session when the exchange stops feeling linear.

You are no longer simply asking a question and receiving an answer. You are no longer even refining a prompt in the ordinary sense. Something else begins to happen. Certain phrases return with altered weight. Certain errors recur, but not identically.

Coherence degrades while fluency improves.

The central problem is not that AI systems sometimes fail. Of course they fail. Nor is the main problem that they occasionally hallucinate, wander, or produce obvious nonsense. Those are manageable problems because they announce themselves early. The more interesting and professionally dangerous problem is that a system can become