PHIL 115 · Philosophical Ideas · Widener University

The Simulation
Semester

An introduction to philosophy taught as a fourteen-week mystery. I set the readings and themes. Claude helped me build the story. Gemini drew it. This is how the course was made, and what happened when we taught it.

architect@simford:~$ Welcome to Simford University. I am the Architect.
  • 14weekly episodes, one per week of the semester
  • 14comic pages, one for each episode
  • 13,000words of story, revised before students read a line
  • 22philosophers on the reading list, all read in primary sources
  • 12short writing assignments set inside the plot

The idea

Give students a reason to ask the question before the philosopher answers it.

Intro courses often run as a survey: Plato one week, Descartes the next, Hume after that. Students meet each argument cold, and the argument has to earn their interest all on its own. And, let's face it, philosophers aren't usually the most captivating writers. For spring 2026 I rebuilt PHIL 115: Philosophical Ideas around a single, semester-long story instead.

Alex Chen, a first-year at Simford University, starts noticing glitches. A squirrel freezes mid-chew for four seconds. A lecture hall stops for everyone except Alex and their roommate. An email from “Architect Support” arrives with one line: Your observant nature has been noted. Alex spends the semester trying to work out what kind of world this is, and what to do about it.

Every week, the students encounter a character confronting a puzzle that we then explore in the week's reading. Alex asks whether a backup of themself would still be them before students read Locke and Parfit on identity. The friends vote on whether to sacrifice fifty-three “instances” to save 3,482 in the week the class reads Mill. A night-shift janitor turns out to have reported the glitches for two years before any student noticed. That's the week we read Fricker on testimonial injustice.

By the time students reach the primary text, they already care how the argument comes out.

The build

Three collaborators with a clear division of labor.

I chose what to teach and had the last word on every page. Claude was a fast, tireless co-writer. Gemini was the illustrator. Here is the sequence, in the order it happened.

  • Instructor
  • Claude (Anthropic)
  • Gemini “Nano Banana” (Google)
  1. 01
    InstructorClaude

    Fix the syllabus first

    I started with my previous version of the course and a brainstorming session with Claude. We identified the core topics I wanted to cover and the primary sources I wanted students to read: the examined life, skepticism, induction, personal identity, mind, free will, three ethical theories, political authority, epistemic injustice, technology, the problem of evil, and the meaning of life.

    The readings were mostly ones I've taught for years, so the story had to serve the syllabus, not the other way round.

    What went in
    • A list of 13 weekly themes that were brainstormed with Claude based on previous versions of the course
    • The primary text for each week, from Plato's Apology to Wolf's Meaning in Life
    • The prompt: build the course as a story (ok, it was more complex than that)
  2. 02
    InstructorClaude

    Brainstorm the arc

    In conversation with Claude, we worked out the premise (a university that might be a simulation, run by an AI called the Architect), a cast of five students and a professor, and a season outline in which each plot turn lands on that week's reading.

    The outline came back as a storyboard: a theme, a reading, a sequence of beats, and a closing hook for every week. The hooks mattered most: each episode ends on a question that's still open when class begins. I tweaked the storyboard until I was happy with the full arc.

    From the brainstorming conversation

    Claude“Awesome, let's turn this into a proper season outline.”

    Week 1 hook, as outlined“Sets tone, introduces Architect & characters, has tiny glitch that can be nothing… or not.”

    Week 4 hook, as outlined“Makes Locke & Parfit immediate: do previous Alexes' decisions bind this one?”

  3. 03
    Claude draftsInstructor revises

    Write the episodes

    Claude drafted each weekly vignette from the storyboard, roughly 900 words apiece. I revised every draft before students saw it, checking that the philosophy was accurate and that each episode set up the questions I wanted to discuss in class.

    Every episode closes with a page from Alex's notebook. Those entries became a model for the students' own writing.

    End of Episode 1

    Alex's notebookDay 1. Something froze. Probably nothing.

    Prof. Reyes asked how much of my life I've actually examined. Honest answer: almost none.

    Maybe this is what philosophy is. Noticing the weirdness instead of ignoring it.

  4. 04
    Gemini

    Draw the comics

    Each finished vignette went to Gemini's “Nano Banana” image model with instructions to render the week's story as a comic page and to keep the characters and the campus consistent from week to week.

    It did an okay job. The style held steady all semester. The characters did not always stay themselves, which turned into a lesson of its own (see the glitches).

    Episode 5, “Backups” Comic page for Episode 5: Priya shows Alex a hidden system panel listing 3,482 active instances; the screen reports an instance save for ALEX_R7.
  5. 05
    Instructor

    Build the course around it

    In Canvas, each weekly module opens with the comic and the episode, then the readings. Twelve micro-writing assignments put students inside the plot: reconstruct the argument Alex keeps circling, object to the group's vote, diagnose what was done to Elena.

    The story gave every assignment a concrete case, so students spent less time inventing examples and more time on the argument.

    A typical week in Canvas

    > Comic page
    > Episode text
    > Primary-source reading
    > Discussion log (after class)
    > Micro-writing, set in the episode

One week, three stages

Episode 3, “The Glitch Log,” from outline to page

Week 3 is Hume on induction. Alex and Jordan think they have found a pattern in the glitches, and they test it.

1 · Storyboard beat

The outline

They notice a pattern: glitches cluster in the engineering building hallway at 3:14 pm and near the library printers.

At 3:14, nothing happens. No glitch, no freeze. Just normal traffic. Sam teases them: “You're seeing patterns where you want to.”

“WARNING: Overfitting detected. Please recalibrate expectations.”

The beat sheet already had the punchline: the system scolds Alex for overfitting.

2 · Finished episode

The vignette

3:13. Nothing.

3:14. A professor walked by carrying coffee. Normal.

3:16. 3:17. 3:18.

“Three data points isn't data,” Sam said gently. “It's coincidence. You saw some weird stuff, you wanted it to mean something, so you found a pattern.”

The episode slows the scene to a countdown and gives Sam the Humean objection in his own words, before students open the Enquiry.

3 · Comic page

Gemini's page keeps the countdown, the hallway, and the warning, and adds a misspelled field label (“Isobject”) on the phone.

The season

Fourteen episodes in four acts.

The acts follow the four units of the syllabus. Select any episode to see its comic page, the question it raises, the readings it sets up, and the writing assignment that went with it.

Act I

Knowledge & Reality

What can Alex know about a world that might be faked?

Act II

Mind & Identity

If there are copies of Alex, which one is Alex, and is any of them free?

Act III

Ethics & Politics

What do the friends owe the people the system treats as expendable?

Act IV

Meaning & Value

Can a designed world, run by a fallible god, still be worth living in?

Read the full episode →
Readings
Writing assignment
Comic page
Open full-size image

The cast

Each character carries a philosophical temperament.

The cast was designed so that disagreements in class had someone to stand behind. Students could argue Maya's side, or Sam's, without having to argue their own.

Alex Chen, brown hair, brown jacket

Alex Chen

Point of view

First-year, curious, a little anxious, smart but not cocky. Keeps the notebook that closes every episode.

Jordan, dark curly hair, teal shirt

Jordan

The hacker-skeptic

Alex's roommate. Loves puzzles and “what if” scenarios, and finds Alex_R5 through R7 in the student database.

Maya, red box braids, JUSTICE pin

Maya

Justice and power

Organizes the movement after the Stability Protocol and keeps asking who ends up on the chopping block.

Sam, blond hair, Campus Ministry shirt

Sam

Faith and meaning

Campus ministry regular and the group's skeptic about the skeptics. Carries the problem of evil in Week 12.

Priya, long dark hair, purple top, at a computer

Priya

Systems and AI

Second-year CS major. Finds the hidden system panel and explains what a backup of a mind would mean.

Professor Reyes, silver-streaked locs

Prof. Imani Reyes

The instructor

Teaches Intro to Reality Studies. First words on the board: REAL. KNOW. DO.

Elena, night-shift janitor, holding a mop

Elena

The one who already knew

Night-shift janitor who filed glitch reports for two years and was told she wasn't “calibrated correctly.”

The Architect, a glowing geometric face

The Architect

The system

The AI that runs Simford. Speaks through screens, emails, and PA systems, and thanks everyone for their participation.

Portraits are cropped from the comics as each character first appeared. Several didn't stay that way. Here's what changed.

The glitches

The illustrator had its own personal-identity problem.

Gemini kept the look of the comic steady all semester: the line work, the palette, Alex's brown jacket. It was far less reliable about who was who. Characters drifted between weeks, details from the script went missing, and the lettering sometimes fell apart. I left the slips in.

Weeks 1 → 6 → 8 → 14
Prof. Reyes in Week 1: a Black woman with silver-streaked locs
Wk 1
The Week 6 lecturer: a gray-haired white man in glasses, suit, and tie
Wk 6
Prof. Reyes in Week 8: a younger woman with dark curly hair in a purple blazer
Wk 8
Reyes in Week 14: an older woman with short gray hair in a lab coat
Wk 14

Prof. Reyes becomes four people

Week 1 introduces her as a Black woman in her forties with silver-streaked locs. In Week 6 the script has “Professor Reyes” lecturing on d'Holbach, and the comic draws a gray-haired white man in a tie. She's a woman again in Week 8, but younger, with dark curls and no locs. By the final episode, where she turns out to be a researcher in base reality, she has short gray hair.

Weeks 7 → 8
Marcus Webb in Week 7: an older man with gray hair and beard
Wk 7
Marcus Webb in Week 8: a young blond man cleaning a window
Wk 8

Marcus Webb gets younger

In Week 7 the Architect shows the friends a photo of Marcus, the janitor, as a gray-haired older man. A week later he's back at work as a young blond man.

Weeks 1 → 9 → 13
Maya in Week 1 with red box braids
Wk 1
The protest organizer in Week 9: straight black hair, purple jacket
Wk 9
Maya in Week 13: curly hair, gray jacket
Wk 13

Maya loses her braids

Week 1 gives her red box braids and a JUSTICE pin. The person holding her megaphone in Week 9 looks like someone else, and Week 13 brings a third version.

Week 4
The counselor drawn as a middle-aged man
Wk 4

Dr. Hayes changes gender

The script gives the counselor a name tag and her pronouns. The comic draws a middle-aged man.

Weeks 3, 8, 9, 11
Speech balloon reading 'Jordan readed win't disbelief?'
Wk 8

The lettering breaks down

“Jordan readed win't disbelief?” is a whole speech balloon in Week 8, beside an enrollment agreement written in near-English. Protest signs read RIIGHTS FOR USS and PROGGED NOW!, and Alex's phone shows a field labeled “Isobject.”

Week 14
A researcher in a lab coat with the same speech balloon shown twice
Wk 14

The same line, twice

In the final episode, a researcher in base reality wonders aloud whether they're crossing lines. Gemini put that balloon in the panel twice.

Why I kept them

A fallible illustrator suited this course.

Week 4 asks what makes someone the same person over time. Here was a running example: if Maya looks different in every appearance, what makes her Maya? Her name, the role she plays in the story, her memories, the megaphone? Students had Locke's question in front of them every week, in the course materials themselves.

Week 11 is about AI systems that reproduce the patterns they were trained on and fail people in ways nobody intended. The comics showed a capable model doing most of the job well and getting the details wrong in ways a careful reader catches. Importantly, students noticed that the race of the characters may have contributed to the glitches and tied this back to potential problems with the training data. That's a fair picture of where these tools are, and students saw it firsthand instead of hearing it from me.

The writing

Assignments set inside the story.

Twelve micro-writings of 400 to 600 words, each practicing one named skill and each built on a moment from an episode.

Every assignment is graded on a short specification checklist rather than points. A submission either meets the specs or gets a path to revision:

✓Meets expectations. Credit earned.
✓−Almost there. One revision allowed within a week.
✗Not yet. Revision required for any credit.

After class each week, students also file a 150–250 word discussion log in three parts: what I contributed, what I learned, and what I'm still thinking about. It's a close cousin of Alex's notebook.

The last micro-writing hands students the pen. They write a page of Alex's notebook from any moment in the story, in Alex's voice, explaining a philosophical concept in Alex's words.

  1. #01Descartes' Method of DoubtEp. 2: Put Meditation I in standard form and explain why the evil demon matters.Argument reconstruction
  2. #02The Problem of InductionEp. 3: Use Hume to explain why the glitch prediction was doomed, and why trying wasn't foolish.Theory application
  3. #03Who Is Alex?Ep. 4: Argue from Locke that Alex_R7 isn't the earlier Alexes, then object.Objection & reply
  4. #04Mind, Body, BackupEp. 5: Reconstruct a dualist and a physicalist answer to “Is my backup me?”Argument reconstruction
  5. #05Free Will and the Scenario TreeEp. 6: Was throwing the phone in the fountain free? Hard determinism or compatibilism.Theory application
  6. #06The Trolley Problem, Simford EditionEp. 7: Build the strongest objection to the 3–2 vote, then a utilitarian reply.Objection & reply
  7. #07Mere MeansEp. 8: Apply the Formula of Humanity to the page-47 consent form.Theory application
  8. #08Legitimate AuthorityEp. 9: Argue for or against the Architect's legitimacy from social contract theory.Argument reconstruction
  9. #09Diagnosing Epistemic InjusticeEp. 10: Name the precise kind of epistemic injustice done to Elena and the workers.Concept diagnosis
  10. #10The Simodicy ProblemEp. 12: Present the Architect's “simodicy,” object with Mackie or Rowe, and reply.Objection & reply
  11. #11Meaning in a SimulationEp. 13: Use Nagel or Wolf to judge whether choosing CONTINUE is meaningful.Theory application
  12. #12In-Character Philosophical ReflectionEp. 14: Write a page of Alex's notebook from any moment, in Alex's voice.Creative application

What students said

From the end-of-semester evaluations.

I loved the format of the ongoing story with episodes… it gave a direct scenario for each philosophical idea we were attacking.
PHIL 116 student
The weekly story… definitely kept the class interesting and engaging.
PHIL 115 student
Readings connected to a narrative… “glitches” that probe philosophical questions.
PHIL 116 student
Micro-writing assignments that were thought-provoking.
PHIL 115 student
How philosophical questions manifest themselves in our daily lives.
PHIL 116 student, on the most important thing learned
It is okay to question the things around you.
PHIL 115 student, on the most important thing learned
A suggestion worth taking
The comic thing was good but… if it were sped up and finished early in the semester as a way to introduce topics… then spend the following weeks diving deeper into each.
PHIL 115 student

Excerpts from anonymous course evaluations, PHIL 115 and 116, spring 2026. Ellipses mark trimmed text.

Try it yourself

What I'd tell a colleague starting this in their own course.

Start from the reading list, and make every plot turn land on a text.

The story has one job: to get students to the primary source with a question already in hand. Decide the readings and their order first. Then ask what would have to happen to a character for that reading to feel urgent that week. If an episode is fun but doesn't set up the text, cut it or rewrite it.

Use the AI as a co-writer, not the author.

Claude drafted quickly and took direction, but every episode went through my revision. Check the philosophy hardest: a character's paraphrase of Kant becomes what students think Kant said.

End each episode on a question.

Alex's notebook gave every week a closing prompt, so discussion could start from a question the story had left open.

Give the image model a character sheet, every time.

An image model only knows what is in the request in front of it. Paste the same physical descriptions into every prompt, and attach earlier pages as references if your tool allows it.

Check every panel before you post it.

Look for faces, names, pronouns, and lettering. Even with good prompts, expect drift. Decide in advance which slips you'll fix and which you'll keep and talk about.

Keep the important words out of the art.

Image models still misspell. Anything students need to read closely belongs in the episode text, with the comic as a companion to it.

Tell students how the materials were made.

Say which parts were drafted by AI and which by you. In a course with a week on AI ethics, the disclosure is part of the lesson.

  Story arc, to adapt
I'm redesigning [COURSE] as a semester-long story.
Here are my weekly topics and the primary
readings for each, in order: [LIST].

Propose a premise and a small cast whose
conflicts map onto these topics. Then give me
a week-by-week storyboard: theme, reading,
5–7 story beats, and a closing hook that sets
up the reading as a question. Don't change or
add readings.
  Comic page, to adapt
Render this week's episode as one comic page,
4–6 panels, in the same style as the attached
earlier pages. Keep every character's look
consistent with this character sheet:
[CHARACTER SHEET]

Use short speech balloons, spelled exactly as
written. Episode text:
[EPISODE]

These are starting templates written for this page, not the exact prompts used to build the course.

Read the whole season.

All fourteen episodes, each with its comic page, exactly as students read them in spring 2026.

Start with Episode 1 →