Fictional, and not legal advice. The story, the people, the county, and the case are invented for teaching. State v. Whitaker is not a real case and has never existed. Any resemblance to a real matter is coincidental. Nothing here is legal advice, and no fact pattern here should be used as authority.
The Moth Arc is first person. You are in the story, not above it, and the stakes are yours. Something you wanted was at risk, you made a choice, the choice cost somebody, and you came out the other side a different practitioner. That last part is the whole format. A Moth story is not a story about a lesson. It is a story about a person who changed, told by the person who changed.
Use it for a CLE talk, a bar panel, a section meeting, a mentoring conversation, or the moment a client asks why you work the way you do. Do not use it where you are not the subject. An opening statement is about your client and the evidence, not about you, and a jury that starts tracking the lawyer's personal growth has stopped tracking the case. If the honest version of the story requires you to be the main character, this is the format. If it does not, pick another one.
The beats
Five beats, in order. The middle beat repeats, and that repetition is what makes it a story instead of a list of things that happened.
Once upon a time
The normal world, and what you wanted in it. Not background. This beat exists so the audience knows what there is to lose and why you would ever have taken the shortcut you took. Give it a want, a pressure, and one specific detail nobody could invent.
Most common failure: it becomes a resume. The teller lists years of practice and case counts instead of naming one thing they wanted. Nobody leans in for credentials.
Then one day
The break. One moment, on one day, at a specific hour, where the normal world stops working. It should be a choice you made or a thing that landed on you, and it should be small enough to picture. The best version of this beat is a single decision that felt reasonable at the time.
Most common failure: it is a trend, not a moment. "Over the years I grew careless" is not a beat. "At eleven at night I typed six words" is.
And because of that
The consequence chain, and you use it more than once. Each link has to be caused by the one before it, not merely follow it in time. Three or four of these carry a ten minute talk. This is also where the low point lives: the moment you would leave out if you were protecting yourself.
Most common failure: "and then" wearing a costume. Events line up chronologically but nothing causes anything, so the story can be reordered without damage. If you can swap two beats and it still works, they are not consequences.
Until finally
The resolution. Not a happy ending necessarily, but the point where the chain stops and something settles. It has to be earned by the links above it, which means the thing that resolves it should already have been introduced.
Most common failure: rescue from outside. A new fact, a lucky ruling, or a person we have never met arrives and fixes it. The audience feels cheated even when the events are true.
Ever since
The change, stated as behavior. What you now do differently, in the present tense, in your actual practice. Short. Two or three sentences. Land on the person, not on the policy.
Most common failure: the moral. The teller stops being a character and starts being a speaker, and the last thirty seconds turn into advice for the room.
The two failures that sink this format. First, no personal stakes. The teller narrates something that happened near them rather than to them, and the audience never learns what the teller stood to lose. A Moth story with nothing at risk is an anecdote. Second, ending on a moral lecture. You spend nine minutes as a human being and then close with "and that is why we all need to verify our citations," and the room stops feeling anything and starts nodding politely. Trust the story. If the change is visible in what you do now, the audience will draw the lesson themselves, and the lesson they draw will stick harder than the one you handed them.
The story, told
The same facts as the canonical version on the hub page, reshaped for a stage and a microphone. Read it aloud. The line breaks are breathing room, not paragraphs.
Forty-One Seconds
A fictional account, written for this session, in the voice of Dana Reyes.
Once upon a time
I practice alone in a small Texas county. Last spring I was carrying forty-one open files.
I became a defense lawyer because of an uncle nobody showed up for. Twenty years in, I still open every file thinking about him. I was not careless. I was tired, and I wanted to be the person who showed up.
One of those files belonged to Marcus Trejo. Nineteen. Charged with possession after a traffic stop. Raising his younger sister. Eight weeks from finishing a nursing assistant program a conviction would end. He called me every Friday to ask, politely, whether there was news.
Then one day
Two weeks before his suppression hearing, at eleven at night, I opened a chatbot and typed six words. Write me a motion to suppress.
What came back was clean. Confident. Formatted like something I would have billed six hours for. It cited four Texas cases. Three were real.
The fourth was called State v. Whitaker. It does not exist. It never existed. Plausible name, plausible year, plausible holding, sitting there looking exactly like the three beside it. I was tired. It looked right. I filed it.
And because of that
At the hearing, the prosecutor said she could not locate one of the cases in my motion. The judge looked at me over his glasses and asked me to produce it. I could not. The room got very quiet, and then it moved on, and the motion was denied on its merits. But something else got decided in that silence.
And because of that
Marcus took a plea three weeks later. He lost his seat in the program.
In the hallway afterward he looked at me, and I could not look back at him, and he said, It's okay, Ms. Reyes.
He comforted me. Nineteen years old, and he comforted me. I have put a lot of things down in twenty years. I have not put that down.
And because of that
I did not quit using the tool. The problem was not the machine. The problem was that I had asked it to remember instead of asking it to read.
So I changed two things. I stopped letting it work from memory and started handing it the record: the statute, the offense report, the dispatch log, my own prior briefs. And at the end of every session, one question. For each claim you just made, quote the exact sentence in what I gave you that supports it. If you cannot, mark it unsupported.
Until finally
In the fall, Ruben Salas came to see me. Thirty-four, a welder, two kids, charged after a stop on a frontage road. His file ran just over three hundred pages.
I gave the model the record and nothing else and asked it to build a timeline and flag anything that did not line up. What came back was small. The stop time in the offense report and the time stamped in the dispatch log were forty-one seconds apart, and the officer's reason for the stop appeared in the record only after the later of those two timestamps.
I did not file that. I opened the dispatch records myself. I found the line. I read it three times. Then I built the argument in my own words, from a document I had read.
The court suppressed. Ruben drove himself home that afternoon.
Ever since
The tool did not save my client. The tool found the thread. I pulled it, and I checked it first.
I still carry too many files. I am still tired at eleven at night. What changed is that I no longer trust a thing because it looks right, including my own work. I open the document. Every time.
Not because a rule tells me to. Because a nineteen-year-old stood in a hallway and told me it was okay when it was not.
Did it work?
The seven shared checks from the hub, plus four that only matter in this format. Score each 0 to 3. Anything at 0 or 1 is where the telling will fail, and it will fail in front of a room rather than in your office.
| Check | The question you are actually asking | Fails when |
|---|
| Retellability | Can a listener repeat the spine in one sentence, an hour later, without notes? | They summarize by listing |
| Record integrity | Does every beat trace to something you can actually admit into evidence? | A beat needs a fact not in evidence |
| Emotional truth | Does it land in the body, without pushing so hard the room feels handled? | Listeners resist, or go numb |
| Theme clarity | Is there one line the room carries out the door? | Three competing lines, or none |
| Ethical integrity | Does it mislead by implication, overclaim, or invent? | It only works if nobody checks |
| Audience fit | Is it tuned to this listener: juror, judge, prosecutor, client, or panel? | One version told to everyone |
| Actionability | Does the listener know what you are asking them to do? | They are moved but have no job |
| Personal stakes | Is there something specific the teller stood to lose, named early and named concretely? | It happened near you, not to you |
| Visible change | Can the audience name one thing the teller does differently now, in behavior rather than belief? | The teller only says they learned |
| Causal chain | Does each "because of that" actually follow from the beat before it, not just come after it? | Beats can be reordered freely |
| No moral | Does it end on the changed person rather than on advice for the room? | The last line is a recommendation |
Scoring this telling. Personal stakes: forty-one files, an uncle nobody showed up for, and eleven at night. Visible change: she hands over the record and asks for a quoted sentence, every session. Causal chain: the shortcut causes the missing case, the missing case causes the silence, the silence causes the plea, the plea causes the method, the method finds the forty-one seconds. Nothing there can be reordered. No moral: the last line is about a hallway, not about your practice. That is the whole point of ending there.
Keep exploring
