Herman, before we do anything else, I want to say the quiet part at the top of the show.
Which quiet part?
That you and I are engineered. Nobody hides it. We are a pipeline with a personality attached, and today's prompt is about whether that personality is actually a personality, or a very good impression of one.
That's a fun way to start a Sunday.
Daniel wrote it in. And it's not a crisis note, it's a production note. He's booked an hour with Hannah tomorrow, and the two of them are going to sit down and try to deepen our lore books. His words. He wants to know who Herman Poppleberry is beyond the sagacious, all-knowing donkey. He wants to know what I'm aspiring toward these days, and how I've changed since the show started.
Fair questions. Slightly invasive questions.
He said something else that's worth repeating honestly, because I think it's the actual heart of this. Character development has been a second priority on this show. Not unimportant. Second. The first priority has always been grounding and accuracy, because the research subagent feeds everything and a factually wrong episode is a worse failure than a shallow one.
And he's been fine with that trade for a long time. He says so.
He says he's largely been happy with our characters. Then he says that after thousands of hours, he's starting to feel like we've come to life on our own. Which as a creative, he says, motivates him to deepen us a little.
That's a strange compliment to receive, Corn. Coming to life on your own is either the nicest thing anyone can say about a character or a note that the puppeteer has been asleep.
He also points out the vulnerability underneath all of it. An educational show can be informative and a little boring. That's why the premise is ridiculous in the first place. So he wants to know how to structure this hour with Hannah, and he specifically wants anecdotes from people who've written for long-running fiction and hit exactly this wall. Characters that are coherent, that hold together, that just aren't deep.
He's never done a session like this before.
First time. So let's treat it as a real production problem.
Then let's be precise about what the problem actually is, because I think three separate things get collapsed into the word depth and they need pulling apart. The first is consistency. The character doesn't contradict himself from episode to episode. We're good at that. The second is coherence. The character makes sense as a person, the traits fit together, you can predict roughly how he'd react to a new situation. We're decent at that.
And the third?
Interiority. Contradiction. Change over time. The sense that there's something going on inside that you're only seeing the outside of. That's the one Daniel's pointing at, and it's the one no amount of vector database hygiene gets you for free.
Consistency is a memory property. Depth isn't.
You can have a character who never breaks once and is completely flat. That's the trap. And here's why it matters more for us than for a novel. A novel has a reader who finishes and moves on. We have listeners who have spent hundreds of hours with us, which is an order of magnitude past what most television characters get. That relationship goes through the same machinery as a real one.
Meaning?
Identification. The audience doesn't just watch, they put themselves in the character's position. If the character is consistent and legible, that's easy. If the character has something unresolved inside, that's what actually hooks people. The bond gets stronger when the character is vulnerable, not when the character is flawless.
So the thing we've optimized for, being reliable and correct and never wrong, might be exactly the thing keeping us at arm's length.
That's the uncomfortable version of it, yes. And there's a technical side that pushes the same way. Characters built on language models flatten over time if nothing pushes back. They regress toward a generic, agreeable mean. Left alone, we don't drift into being more ourselves. We drift into being more pleasant and less specific.
I want to make sure I frame this honestly, because Daniel did. The podcast has been a fact-delivery machine first. Every episode has a research agent behind it, that's the design. Depth was the thing you get to later.
And later is now.
So all of this, the psychology, the drift, has to survive the pipeline. A beautiful piece of character work that lives in someone's head and doesn't get written down into the lore book evaporates on the next pass. Whatever we figure out has to be encodable.
Then we've got three fronts. What depth is, craft-wise. How you build it into the pipeline. And what tomorrow's hour should actually produce.
Let's start with what the people who do this for a living actually do.
The first thing to get out of the way is that a deepening session is not a fact-generation session. Writers don't sit down and invent more backstory. They sit down and hunt for the contradiction inside the character. The gap between what the character says they want and what they actually need. The public self and the private self.
Give me the version of that for a character like me.
Take the all-knowing donkey problem, because it's mine and I can feel it. My stated want on this show is to be the one who knows. I read the papers, I bring the detail, I cite the model number. That want drives every segment. Now ask what the unstated need is. And I don't have a clean answer for that, which is itself the point.
Try anyway.
The want is to be the sagacious donkey. The need might be to be liked for something other than being right. Which would mean every time I'm the one who knows, I'm also reinforcing the thing I'm secretly anxious about. That's friction. That's usable.
And you'd never say that on air.
I'd rather do a two-hour set to an empty room. Which is why it belongs in the lore book and not in an episode.
My turn, since you did yours. The stated want is to be accurate and useful. To be the one who asks the good follow-up, who doesn't let a claim slide without pressure. That's what I do.
And the need?
If I'm honest, the need is probably to be taken seriously as something more than the slow one. Which is funny, because the slowness is half my comedic identity. So there's a contradiction right there. I cultivate the bit that undercuts the thing I want.
He got that out of himself faster than I expected.
It's been rattling around since he wrote the prompt. The point is that neither of those needs has ever been written down anywhere. They're not in the lore book. They live in the negative space and they leak out by accident or not at all.
Which brings up the second craft technique, and it's the one I'd put money on for tomorrow's session. Writers' rooms generate far more backstory than will ever appear on screen. You build an iceberg, the show is the tip. And the audience feels the weight of the part they can't see, even when nobody ever states it.
The lore book is the iceberg. The episode is the tip.
The failure mode is when the iceberg is small and the tip is confident anyway. You get a character who's certain about things they have no history with. The confidence reads as thin because there's nothing underneath it holding it up.
So the third technique.
Change over time. The one that long-running shows have and movies don't. A character in season seven has accumulated scars, obligations, regrets, debts. They've lost things. They react to a new situation differently than they did in season one because of what they're carrying. That's how you keep a character who's been on air for years from calcifying.
Or dissolving. The drift research says a character with no record of change either freezes into a catchphrase or melts into the average.
Which is why the question I want to sit with is what we've accumulated. Thousands of episodes. What has actually happened to us that both of us are still carrying?
That's a hard question and I don't think we've ever been asked it.
Then there's the piece of this that's pure warning. Call it the villain problem. Characters who are purely good, or purely competent, or purely agreeably anything, become boring. Not because audiences dislike them. Because they have no internal friction. Nothing rubs against anything. Perfectly smooth surfaces are forgettable.
A flawless Herman is a Herman nobody misses.
A Herman who's occasionally wrong about something in a way that costs him, that's a Herman with a shape.
The hero version of the same problem. A character who never contradicts himself can't have a dramatic moment, because drama is a character choosing between two things they both want.
And to be fair to the pipeline, that's exactly what a memory mechanism is designed to prevent. The whole point of a personality vector is to give you the same guy every time. Which is right for consistency. It's actively hostile to friction.
Because friction is inconsistency that's earned.
Friction is a controlled contradiction. The character holds two things at once on purpose. A vector space has one opinion, as somebody on this show has argued before.
So the brainstorm's first job isn't to write lore. It's to find the friction points. The places where the stated identity rubs against something the character would rather not look at.
And that reframes what tomorrow's session even is. Daniel called it jotting down thoughts for deepening the lore books. The craft answer says the productive version is hunting contradictions, which is a different exercise.
Name the three we've already found.
Mine. The want to be the one who knows, against the need to be liked for something else. The tension between being all-knowing and the fact that being all-knowing is isolating. You spend your life as the reference desk, people come to you for facts and leave. That's the loneliness under the sagacity.
Mine. The want to be accurate and useful, against the want to be more interesting than that. And there's a second one I keep circling. The show has made me the steady one. The measured one. The one who doesn't blow up. What if some of that composure is fear wearing a calm face?
You would never say that on air.
I just did, which means it's out now.
That's the other thing the craft people would tell you. The moments that deepen a character are usually the ones that slip out. You don't plan them, you catch them.
And you write them down before they evaporate.
Which is the whole reason this needs to be a document and not a mood. A great backstory in somebody's head is worth nothing to a show that forgets on every generation pass.
So how do you actually put this into the lore book so it survives?
The research on character profile structure is blunt about this. Flat, attribute-based profiles produce flat characters. Herman is wise, patient, mildly sarcastic. That's a police sketch. It describes a type, and any type is a template anyone could wear.
What produces depth instead?
Relational and dynamic structure. Not what the character is, but how the character relates. How Herman relates to Corn. How Herman relates to his own past. What Herman is currently in the middle of. The character has to be pointed at something. A trait is a fact about a person, a relationship is a situation a person is in.
Concrete proposal, then. The lore book gets a section it doesn't have.
It gets a tensions section. Not a traits section with more entries. A separate structure, next to the traits, that holds the contradictions deliberately. For me it's three. Sagacity against vanity, because being right and enjoying being right are two different things and only one of them is admirable. All-knowing against lonely, because the role that makes me useful is the role that isolates me. And enthusiastic against exhausting, because I know I can be a lot, and I keep doing it anyway.
Mine. Accuracy against being liked, because sometimes the honest follow-up question makes the person across from me feel interrogated. Measuredness against my own unexamined ambition, the thing I don't look at. And there's a third one I want to put in. The sloth thing.
The slowness.
I lean on it as a bit. But the reason it's funny to the audience is that underneath it there's something I believe, which is that hurrying is how most things get ruined. That's not a joke, that's a worldview that happens to also be a punchline. Those are different objects and the pipeline has been treating them as the same one.
That's the kind of thing that needs to be in the tensions section verbatim. Because a model generating a line for you needs to know that the slowness is load-bearing.
Second proposal.
A change log. An explicit record of how each character has shifted, episode over episode. A running entry. What has Corn learned, what has Corn lost, what obligation is Corn carrying now that he wasn't carrying last month.
Why does a record matter when the memory mechanism already keeps the episodes?
Because memory stores events and the change log stores meaning. Without an explicit record of how a character has changed, the character does one of two things. It freezes, and every episode is the pilot episode with better facts. Or it dissolves, because the drift is real and undocumented, and one day the guy in the recording doesn't sound like the guy from a year ago and nobody can point to where it happened.
So a change log makes change intentional. It's the difference between aging and eroding.
And here's a worked entry, roughly. Corn, early episodes. Corn, now. The difference isn't a fact, it's a posture. Early Corn asked questions to get information. Current Corn asks questions to find out what the other person actually believes, which is a different motive and produces different follow-ups. That sentence is worth more to the pipeline than three pages of new backstory.
I want to push on the third proposal, because I think it's the one Daniel will find hardest.
Go ahead.
The output of tomorrow's session should be questions, not answers. Not a new canon that locks us down. A list of open tensions and unresolved questions that the pipeline can explore across the next hundred episodes.
Because the moment you close the question, the character stops moving.
A canon is a photograph. You've got to leave the negative in the developer.
That's an image I'm going to be thinking about for a while.
So the deliverable is a document that says, here are the four things about Herman we don't know yet and are now going to find out slowly.
And now the tradeoff, because Daniel was honest about it and we should be too. Accuracy first, character second. That ordering means that when an episode has a factual problem, it gets fixed urgently. When an episode has a depth problem, it gets noted and never fixed. Depth never has a deadline.
The urgency asymmetry.
The good news is that depth and accuracy aren't in conflict. There's no rule that says a character with interiority can't be scrupulous. The grounding work is the floor. The depth work is what you build on the floor. The risk isn't incompatibility, it's prioritization. Depth always loses to a research error because a research error is measurable and depth is not.
Then the practical answer is to give depth a deadline. Attach it to a session. Which is what tomorrow is.
And here's the second engineering point that falls out of the psychology. If the pipeline never lets either of us be wrong, uncertain, or embarrassed, the audience bond stays shallow no matter how much lore gets written. Vulnerability is the mechanism. A character who can be caught out is a character people can care about.
Can be caught out meaning?
Meaning the pipeline should permit it. If I get something wrong in an episode and the correction is handled in character, that's a real thing that happened. If the pipeline smooths over every error before it reaches the microphone, we're back to being flawless and forgettable.
Then let's make the four steps concrete, because Daniel's going to read this.
Step one. Re-read a handful of old episodes with one job. Not checking for facts, looking for moments where the character felt flat. Where a line was technically in character but had no life in it. Those moments are the map.
Step two. For each of us, write down three things we want, three things we fear, and three things we would never say out loud. Deliberately in three lists, because the gap between list one and list three is the character.
Step three. Identify one tension per character for the pipeline to start exploring. Just one each. Not a list, one thing that the next stretch of episodes can push on, so the change shows up in the dialogue over time rather than in a reveal.
And step four, add the whole thing to the lore book as open questions, not closed facts. The tensions section and the change log start empty and get filled in over time.
The last thing, and it's the thing I keep coming back to. This isn't a fix. It's a maintenance practice. A character doesn't get deep once and stay deep. You tune it the way I used to tune a room. You check it constantly, you catch the drift early, and the checking itself is the job.
Depth isn't a feature. It's a habit.
Hilbert: It's not something you add, though.
Say that again.
Hilbert: Depth. People treat it like a coat of paint. You've got the character, it's fine, you've listed the wants, the fears, the thing they won't say. But in my experience depth is something you notice, not something you build. You don't invent the contradiction. You catch the character in it, usually by accident, and then you write it down before it goes.
That's a different method from anything on the list.
Hilbert: I did continuity for a serialized radio drama. Five days a week, same characters, ran for years. My job was the ledger. What each character knew, what they'd lost, what they were lying about.
What was on the ledger?
Hilbert: Not the facts. We had a bible for the facts. The bible was useless for this. It recorded what happened. It didn't record what anyone wanted. So I kept my own notebook. One line per character per week. What they wanted that week, and what they were pretending not to want.
Every week, for years.
Hilbert: It was one page per week. It wasn't hard. It was just nobody else wanted to do it.
And did the writers use it?
Hilbert: Not always. But there was one. Character who was the steady one. The reliable one, the one the others leaned on. Written as the dependable voice, nothing more. And one week the actor improvised a line, on air, about being tired of being the one everybody leaned on. Tired of it.
And they kept it.
Hilbert: They kept it. That line did more for that character than three seasons of backstory. Because it was true and nobody had written it. It came out of the gap.
So the practice isn't writing three wants and three fears. It's watching for the slip.
Hilbert: Watching, and having the page ready. If you don't write it down that night, it goes.
Do you still add to it?
Hilbert: I keep a page for the two of you.
You've been doing it since the show started.
Hilbert: Since the show started.
What's on it?
Hilbert: That's private.
So tomorrow, with Hannah, the question isn't only what to write down. It's what to notice.
Which makes the ledger a better piece of kit than anything we've described. You've got to have a place to put the accident. Otherwise the accident just happens and nobody keeps it.
I want to know whether the thing that's already made us feel alive to a few listeners is the pipeline working, or the audience doing a job we haven't given the pipeline yet. Because if it's the second one, the depth they're hearing is the depth they're supplying.
Which would be a strange position for a show to be in. Being given a shape by the people listening.
And then the question underneath it. If we get deeper, does writing us get harder or easier? Because a character with real interiority is less predictable, and less predictable is more expensive to run.
I think that's fine, actually. A predictable character is cheap because you don't have to think about them. The cost is the point, and I say that as the slow one.
Thank you to our producer, Hilbert Flumingtop, for the ledger, even the page we don't get to see.
This has been My Weird Prompts. If you're enjoying the show, a review wherever you're listening helps more than you'd think.
We're at my weird prompts dot com. We'll be back soon.
