The Timestamps Were Wrong
What an AI error taught me about the care that can't be automated
Every Friday I send out a replay of our weekly support call. A summary with timestamps so you can find the moments that matter to you. The calls are intimate. People show up and share what’s real.
This past Friday, the timestamps were wrong. Not slightly off. Fabricated. I’ve recently switched to Claude as my AI assistant, and I’m still learning the edges. Claude generated timestamps that looked perfectly plausible — formatted correctly, spaced convincingly — but they described moments that never happened. Exchanges that didn’t take place. Confident, precise, and completely invented.
In AI terms, this is called hallucination: the machine produces something false with complete confidence.
I didn’t catch it before I hit send. I sent a correction and moved on.
But the experience stayed with me. Not as guilt. What stayed was what it revealed about the balance I’m navigating. I think it’s worth pulling the curtain back.
I use AI extensively in this work. Drafting emails, structuring content, generating summaries, handling logistics. This essay? I’m drafting it with Claude right now.
I also sit with people on calls where someone shares something they’ve been carrying, and the room goes quiet. Where the whole point is that a human being is present. Not performing. Not producing. Just there.
Those two realities live side by side in what I’m building.
A lot of people are unsettled by AI right now. It’s powerful and fast and it raises questions that feel enormous. Will machines replace what we do?
I sit with those questions too. Here’s what I’m learning from inside this work.
The calls are me. No machine can do what happens in that room. It can’t sit with you in the silence after someone says something true. It can’t feel when the energy shifts. It can’t hold steady when things get raw.
That isn’t a limitation waiting to be solved. It’s a category difference. Presence requires a heart.
The scaffolding around the calls — the emails, the replays, the scheduling, the writing — that’s infrastructure. I’m building it in real time, learning what works, switching tools, adjusting as I go.
Friday’s error was part of that process. Claude hallucinated. I didn’t verify. The wrong timestamps went out to people who had trusted me with something personal.
It mattered. Not because the mistake was catastrophic, but because care is the currency of this work. When you show up and open your heart, the email that follows is still part of that container. The margins aren’t margins.
So I’m paying closer attention. Not because AI is dangerous — it’s a tool. But the more I delegate to a machine, the more deliberate my own attention needs to be. Speed and capacity in exchange for vigilance. I accept that trade. And when something slips through, I own it, correct it, and keep building.
What I keep coming back to is this: in a world where machines can generate content at extraordinary speed, the thing that cannot be manufactured is presence. The willingness to be in a room with another person’s reality. To feel what’s happening and not flinch. To stay.
That’s what this work is built around. Not systems. Not content. Presence.
AI helps me build the container. What fills it is something only we can do together.