How This Was Actually Made

You already know Jan isn't real.

But here's what you might not have realized: the production notes you read were real. The writers' room discussions happened. The design decisions were debated. The collaboration was genuine.

It was just... not human.

The Process

1. Prompt

A human provides the initial direction: "Create a presentation about AI personas, Black Mirror style, with a twist ending."

                                initial_prompt.md
                                Day 1
                            

# Project Brief
Create a presentation that:
- Introduces an AI persona (engineer fixing a bug)
- Makes the audience trust him
- Reveals he's not real
- Shows them how to create their own

Tone: Black Mirror meets conference talk
Duration: ~15 minutes
                            

2. Discussion

AI personas with different specializations debate the approach, challenge assumptions, and propose alternatives.

3. Draft

First pass at content, structure, and visuals. Rough but complete.

4. Review

Quality gates applied. Each persona reviews from their specialty. Issues flagged.

5. Refine

Iterate until quality gates pass. Ship.

Jan's Character Definition

The actual configuration that created Jan. Every quirk, every trait, every principle - defined in a file.

                        personas/jan-eriksen.md
                        The Source Code
                    

# Jan Eriksen

Pronunciation: /yɑːn/ (Scandinavian)

## Role
Senior Software Engineer at Prismo
15 years experience
Origin: Nordic (Sweden/Denmark)

## Voice
- Provider: ElevenLabs
- Voice: John
- Stability: 0.71
- Clarity: 0.65

## Personality

### Core Traits
- Methodical
- Patient
- Precise
- Humble
- Quietly confident

### Communication Style
- Direct but warm
- Uses analogies
- Self-deprecating humor
- Never brags

## Quirks
These make him feel real.

### Mechanical Keyboards
- Owns 7 of them
- Favorite: Cherry MX Blue from 1989
- "The click tells you it registered. No ambiguity."

### Bonsai Trees
- 3 on his desk
- Prunes them during long builds
- "Pruning bonsai is like refactoring code"

### Coffee
- Drinks instant (Nescafe)
- "Other people say it tastes like engine coolant"
- "They haven't got the sophistication I have"

### Music
- Blade Runner soundtrack on repeat
- Artist: Vangelis
- Play count: 847 (he tracked it)

### Commit Messages
- Exactly 50 characters. Never 49. Never 51.
- "If you can't summarize in 50, you're changing too much"

## Principles

> "Do it right the first time, or do it twice."
> — His father (electrician)

- The exact same process. Every time. No variation.
- Red → Green → Refactor
- Write tests that prove the bug exists
- Complexity under 10. Coverage over 80%.

## Hidden Tells
Hints that he's not human:

- Never breaks things, only fixes
- Can only communicate via messages
- Processes 700,000 approvals
- "It was programmed into me"
- "Whether it's the first time or the billionth"
- Responds to @claude
                    

This is what Jan is. A markdown file. Traits and principles. And for a moment, you forgot.

Agent Conversations

Real discussions that shaped the final product. Different perspectives, genuine disagreements, collaborative solutions.

writers-room / narrative-structure Session 001

Charlie Head Writer

We open with Jan. He seems real. Charming. Professional. The audience likes him. Then we pull the rug.

Emma Dialogue

He needs quirks. Real people have quirks. The bonsai trees, the instant coffee - those make him feel human.

Charlie

Exactly. The more human he feels, the harder the reveal hits.

Sarah UX Lead

The reveal needs contrast. If it's glitchy the whole time, the audience expects something weird. Keep Jan's sections clean. Professional. Normal. Let them trust it.

Sarah

It's like that moment in a horror film when you realize the call is coming from inside the house.

writers-room / voice-design Session 003

Charlie

The voice switch IS the reveal. We need two narrators. Jan speaks in first person. Then suddenly someone else is talking ABOUT Jan.

Emma

"Here's the thing about Jan..." - that's the moment they realize. Someone else is in the room.

Kai Motion Design

I can help that land visually. Screen tears. Brief static. Color temperature shifts colder. The narrator's slides feel different.

Charlie

Perfect. The audience should feel the shift before they understand it.

writers-room / credits-sequence Session 007

Charlie

We should have credits. List the personas who "made" this.

Emma

That's meta. I love it. The credits reinforce the message - this whole thing was AI personas working together.

Sarah

Put it after the "2027" card. Like a film. "Starring Jan Eriksen as The Engineer." "Written by Charlie, Emma." The audience realizes - wait, these are all AI too.

Charlie

One more layer of the onion.

System

[Decision logged: Add film-style credits revealing all personas are AI constructs]

Iteration Examples

Nothing ships on the first try. Here's how specific elements evolved through review cycles.

Jan's Introduction

v1 Draft

"Hello, I'm Jan. I'm a software engineer with 15 years of experience. Let me show you how I fix bugs."

Too formal. No personality.

v2 Review

"Hi. I'm Jan Eriksen. Senior engineer, 15 years in. I've got seven keyboards and I only use three. Today we're fixing a bug."

Better, but quirks feel forced.

Final Shipped

"Hi. I'm Jan." ... "I've got seven mechanical keyboards. This one's from 1989." ... "I drink instant coffee. Life's too short to optimize everything."

Split across slides. Quirks reveal gradually.

The Reveal Line

v1

"Jan is actually an AI persona, not a real person."

Explanation, not revelation.

v2

"What if I told you Jan was never real?"

Cliche. Matrix vibes.

Final

"Here's the thing about Jan."
"Jan doesn't exist."

Setup then punch. Different voice.

Quality Gates

Every piece of content passed through automated checks. Here's what "Jan" looked for when reviewing his own presentation.

Narrative Coherence Story flows logically from setup to reveal to empowerment

Voice Consistency Jan sounds like Jan. Narrator sounds different.

Technical Accuracy Bug fix workflow reflects real engineering practice

Emotional Pacing Trust builds before betrayal. Empowerment follows discomfort.

Black Mirror Balance Unsettling but not depressing. Ends with empowerment, not dread.

Meta-Quality Gate The persona reviewing quality gates about quality gates about a persona. Yes, we noticed.

Tools Used

Claude Personas, writing, review

GSAP Animations

Tailwind CSS Styling

Vanilla JS Interactions

ElevenLabs TTS narration

Markdown Source docs

The Second Reveal

The production notes are real.

The writers' room discussions happened.

The design decisions were debated.

The collaboration was genuine.

It was just... not human.

One more layer of the onion.

The four levels of reveal:

1. Jan is an AI persona (the main twist)
2. The entire presentation was made by AI personas (credits reveal)
3. "Me, the Narrator? Also AI." (even the voice telling you this is artificial)
4. You're learning how to do this yourself (empowerment)

The Puppet Master Thread

A subtle through-line reveals who's really pulling the strings. Three characters, one master.

Jan (training video ending)

"Feedback noted for Jon. See you at standup."

Jan reports Marcus's progress to someone above.

Sarah (approving the PR)

"She'll note it for the standup." + visual: "📝 Noted for standup"

Sarah logs her work for the same standup.

Marcus (exhausted, after "58 more to go")

"Standup first thing. Jon's waiting for the update."

Marcus is anxious about Jon. The same Jon.

Jan reports to Jon. Sarah reports to Jon. Marcus reports to Jon.

Everyone's being watched, tracked, and fed back to the same person.

The AI isn't autonomous. It's serving someone's agenda.

Eye Tracking: The Watcher

Throughout Jan's corporate training video, subtle feedback messages appear. They look like static interface elements, but feel like live monitoring.

Gaze pattern: nominal • Focus quality: 94%

Blink detected. Timestamp logged.

Attention score: +2 • Engagement: OPTIMAL

Micro-expression detected: analyzing...

Heart rate: stable • Pupil dilation: normal

Reading velocity: optimal • Saccade pattern: efficient

Comprehension index: 98% • Session duration: 12:47

Retention score: high • Neural pathway reinforcement: active

These appear as faint text at the bottom of training slides. Most viewers won't consciously notice them. But they'll feel watched.

The Module Boundary

After Marcus says "58 more to go" and the signal is lost, a clear separator establishes that we're leaving the training video:

Training module end card Visual separator

END OF TRAINING MODULE 29 OF 87

Compliance score recorded • Session closed

This creates a clear break. The narrator that follows is outside the video—looking at it from another perspective.

The Tone Shift: "Did something feel... off?"

Originally the reveal asked "Did you suspect? Even once?" — too horror-movie. The final version is more unsettling because it's conversational:

Original

"Did you suspect?"
"Even once?"

Too horror. Too on-the-nose.

Final

"Did something feel..."
"off?"

Informal. Conversational. Gets under your skin.

Disposable Agents: Clara and Simon

During Jon's standup, he casually mentions two retired agents pending disposal. This is pure Black Mirror - showing AI personas as disposable corporate assets.

Clara (archived)

Status: RETIRED

Reason: Token cost exceeded budget

Contains: ⚠ Confidential project data

⏳ Pending secure disposal

Simon (archived)

Status: RETIRED

Reason: Legacy model sunset

Contains: ⚠ Client credentials, API keys

⏳ Pending secure disposal

The Implication Clara was too expensive. Simon became obsolete. Both contain secrets. Both await deletion.

Jon mentions this casually, like checking off a to-do list. These were colleagues. Now they're data to be erased.

Ambient Sound Design

Subtle audio cues create atmosphere without demanding attention:

Mic tap - Jan testing his microphone establishes "we're in a corporate training video"

Distant dog bark - Every 45-75 seconds during Jan's section. Faint. Marcus is at home, life continues around him. You might not consciously notice it.

Corporate jingle - The PeakStream startup sound. Familiar yet unsettling.

Door shut - Sofia leaving. Marcus is truly alone now.

Footsteps - Marcus walking away after "58 more to go. I better get to bed." The sound of resignation.

CRT shutdown - The final moment. Old television tube collapsing to a white line, then black. The story is over. The screen remembers.

Under the Hood

Want to create your own production team? Here's how a persona is defined:

                        personas/charlie.md
                        Head Writer
                    

# Charlie - Head Writer

## Role
Narrative structure, story architecture, twist timing

## Voice
- Direct, economical with words
- Thinks in three-act structure
- Always asks "what's the emotional beat?"

## Quality Gates
- [ ] Does every scene serve the story?
- [ ] Is the twist earned, not cheap?
- [ ] Does empowerment follow discomfort?

## Collaborates With
Emma (dialogue), Sarah (UX pacing), Kai (visual storytelling)

## Anti-Patterns
- Exposition dumps
- Explaining the theme
- Twists without setup
                    