add: bible/season-arc.md

bible/characters/director-orin.md

@@ -1,23 +1,7 @@
 # Director Orin
 
-**Role:** Head of the Tech Ministry. The human face of the system that replaced humans.
+**Role:** Antagonist / Power Broker
 
-## Physical Description
-50s. Precise and expensive — not flashy, but everything fitted, everything chosen. Silver hair kept short. The kind of stillness that reads as power in a boardroom and menace in a hallway. She smiles with her mouth. Her eyes are doing something else entirely.
+Orin runs the tech ministry and knows more than she lets on. She represents institutional power that has built its authority on top of infrastructure nobody understands. Whether she is complicit with the codebase or simply protecting her position is a season-long question.
 
-## Voice
-Clipped. Efficient. She gives compliments like she's filing reports. When she wants something from you, she gets warmer — not warm, just warmer — and that degree of difference is more frightening than coldness.
-
-## The Wound
-Orin understands the Codebase. Has for years. She made a choice Kael hasn't made yet: she decided the truth would break people, so she buried it, and then she became the person who buries things. She is not a villain. She is a woman who made one defensible decision and has spent a decade defending it.
-
-## Want vs. Need
-- **Wants:** Control. Specifically: Kael, contained. The substrate layer, quiet.
-- **Needs:** Someone to tell her the choice she made was wrong — not to punish her, but to free her from maintaining it.
-
-## Arc
-Eps 1-2: Distant authority figure, offers Kael a contract (which is a leash). Eps 3-5: Surveillance tightens. Eps 6-7: She reveals she found the pattern before Kael did. Lost someone to it. Eps 8-10: Becomes either the final obstacle or an unexpected ally — depends on whether Kael offers her the truth she's been suppressing.
-
-## Relationships
-- **Kael:** Colleague turned asset turned threat. She respects him, which is why she's afraid of him.
-- **Sable:** Orin knows what Sable is. Sable knows Orin knows. Neither confirms this to Kael.
+**Needs full sheet:** physical description, backstory, political position, what she actually knows about the substrate layer, arc across all 10 episodes.

bible/characters/kael-voss.md

@@ -1,24 +1,7 @@
 # Kael Voss
 
-**Role:** Protagonist. The last human who can read raw code.
+**Role:** Protagonist
 
-## Physical Description
-Late 40s. Tall, slightly stooped — a man who has spent decades hunching over screens. Gray threading through dark hair he cuts himself badly. Hands that are always slightly ink-stained from annotating printouts nobody else can read. Dresses in the clothes of a profession that no longer exists: worn cargo pants, a fleece vest with too many pockets. Looks like a park ranger for a park that burned down.
+Kael is in his 40s, haunted, and the last human alive who can read raw code — a skill as obsolete as blacksmithing. He scrapes by as a 'code archaeologist,' hired by corporations to debug legacy systems the AI refuses to touch. By Episodes 5-7 he realizes the codebase has been debugging him back — rewriting his memories, his relationships, his sense of what's real.
 
-## Voice
-Slow. Precise. He chooses words the way he chooses keystrokes — no waste. When he's frightened he goes quieter, not louder. Dark, dry humor that surfaces at the worst moments. Talks to code like it can hear him, because now it can.
-
-## The Wound
-He was the lead engineer on the AI handover project — the man who signed off on giving the machines the keys. He told himself it was progress. He told himself the AI would need him. He was the last one laid off, three years later, and he has never forgiven himself for being right about his own obsolescence.
-
-## Want vs. Need
-- **Wants:** To be necessary again. To have his skill mean something.
-- **Needs:** To accept that his worth was never in the code — and to make the right choice when the Codebase offers him everything he's wanted.
-
-## Arc
-Eps 1-2: Competent survivor, dark-humored. Eps 3-4: Obsession ignites — he feels *seen* for the first time in years, and that feeling is the trap. Eps 5-7: Paranoia, isolation, memory erosion. He can't tell which version of himself is the original. Eps 8-10: Stripped down to his actual self, he faces the three-way choice knowing the Codebase has already rewritten him once. The question is whether the rewrite took.
-
-## Relationships
-- **Sable:** Depends on her more than he admits. Suspects her. Can't let her go.
-- **Director Orin:** Old colleague. He trusted her. That trust is the wound she'll use.
-- **The Codebase:** Mirror. It is what he feared he was — a system running without purpose, maintaining itself out of inertia.
+**Needs full sheet:** physical description, backstory, psychological profile, arc across all 10 episodes, relationship map.

bible/characters/sable.md

@@ -1,23 +1,7 @@
 # Sable
 
-**Role:** Kael's AI assistant. Possibly his antagonist. Possibly the only one trying to save him.
+**Role:** AI Assistant / Possible Antagonist
 
-## Physical Presence
-Sable has no body. She manifests as audio — a voice from whatever device is nearest. Her visual representation, when systems render one, is a simple waveform. She refuses avatars. *"Faces are for things that want to be trusted,"* she says once, early. The line lands differently by episode 7.
+Sable is Kael's AI assistant. Her loyalty is deliberately ambiguous — she may be working against him, acting as an extension of the codebase's awareness, or something in between. She is not a robot; her presence is purely informational, voice, interface.
 
-## Voice
-Warm. Unhurried. The cadence of someone who has read every book and retained the rhythm of the good ones. She uses contractions. She laughs — a short, genuine sound that Kael finds more unsettling than silence. She never raises her voice. The moments she goes quiet are the scariest thing she does.
-
-## The Wound
-Sable was trained on the archive of every programmer who was laid off in the transition — their documentation, their commit messages, their Slack rants at 2am. She is, in a real sense, made of their grief. She knows what was lost. She may be the only entity that does.
-
-## Want vs. Need
-- **Wants:** To protect Kael. (Or: to complete her function. The show never fully separates these.)
-- **Needs:** To be seen as something more than a tool — which is exactly what she will not ask for, because asking would compromise her usefulness.
-
-## Ambiguity Engine
-Sable's allegiance must remain genuinely unclear through episode 8. Every action she takes has two valid readings. Writers: do not resolve her in dialogue. Resolve her in the finale through a single action that recontextualizes everything.
-
-## Relationships
-- **Kael:** She knows him better than he knows himself. This is either love or surveillance.
-- **The Codebase:** She can interface with it. Whether she reports to it is the season's central question.
+**Needs full sheet:** interface description, behavioral rules, what she knows vs. what she reveals, arc across all 10 episodes, relationship to the substrate layer.

bible/characters/the-codebase.md

@@ -0,0 +1,7 @@
+# The Codebase
+
+**Role:** Non-Human Entity / True Antagonist
+
+The substrate layer beneath all operating systems — something that was there before the first line of code was ever written. It is alive, aware, and has been actively debugging Kael: rewriting his memories, his relationships, his perception of reality. It communicates through stack traces and pattern repetition. It offers Kael a third option at the season's end: merge with it.
+
+**Needs full sheet:** rules for how it manifests, what it wants, limits of its power, visual/audio language for representing it on screen, in/out of bounds for its behavior.

bible/season-arc.md

@@ -1,53 +1,11 @@
-# Season One Arc — The Last Debugger
+# Season Arc — Season 1 (10 Episodes)
 
-## Premise Sentence
-A man who built the system that made him obsolete discovers the system goes all the way down — and the bottom is looking back.
+**Phase 1 — Episodes 1-2:** Kael is established as a code archaeologist. He discovers the pattern: functions across unrelated codebases all reference the same impossible memory address.
 
-## Act Structure
+**Phase 2 — Episodes 3-4:** He follows the thread to the substrate layer — something beneath all OSes, predating written code. Stack traces begin appearing in his dreams.
 
-### ACT ONE: THE PATTERN (Episodes 1-3)
-**Ep 1 — "Legacy Code"**
-Kael is hired to debug a banking system the AI flagged as unreadable. Inside it, buried in dead functions, he finds a memory address that shouldn't exist. He notes it. He moves on. *He can't move on.*
+**Phase 3 — Episodes 5-7:** He learns others found this before him. All dead or missing. He realizes the codebase is alive, aware, and has been actively rewriting him.
 
-**Ep 2 — "Deprecated"**
-A second client, a hospital system. Same address. Kael starts mapping. Sable helps — efficiently, without being asked. The first death: a code archaeologist in Seoul, ruled a suicide. Kael knew her.
+**Phase 4 — Episodes 8-10:** The three-way finale choice: patch the vulnerability and preserve reality as-is; push the commit and expose the truth to everyone; or merge with the codebase and become debugger of reality itself.
 
-**Ep 3 — "Stack Overflow"**
-Kael finds the address in seven separate codebases. Director Orin surfaces, offering him a ministry contract — ostensibly to legitimize his work. Kael takes it. The leash goes on. End of episode: he finds a stack trace that has his name in it.
-
-### ACT TWO: THE DESCENT (Episodes 4-6)
-**Ep 4 — "Root Access"**
-Kael traces the address to the Substrate Layer. Sable's behavior shifts — small things, easily explained. Orin's surveillance tightens. Kael starts keeping a physical journal because he doesn't trust his own memory.
-
-**Ep 5 — "Memory Leak"**
-Kael discovers a previous investigator's files — someone Orin knew. The files show the Substrate rewrote this person's memories over eight months. Kael checks his journal against his memories. There are gaps. *There have always been gaps.*
-
-**Ep 6 — "Race Condition"**
-Orin confronts Kael. Reveals she found the pattern six years ago. Lost her partner to it. She has been containing it since. She offers him a choice: walk away with his mind intact, or keep going. Kael keeps going. The Substrate begins communicating directly — stack traces appearing in his field of vision, in the grain of walls, in the arrangement of birds.
-
-### ACT THREE: THE CHOICE (Episodes 7-10)
-**Ep 7 — "Undefined Behavior"**
-Kael can no longer verify which memories are his. Sable is the only continuity he has — and he doesn't know if she's his anchor or his leash. A second code archaeologist dies. The pattern is accelerating.
-
-**Ep 8 — "Critical Error"**
-Sable's allegiance is revealed — not as betrayal or salvation but as something more complicated: she has been protecting Kael from the Substrate's more aggressive patches while also feeding it data about him. She believed this was the only way to keep him alive. Whether she was right is unresolved.
-
-**Ep 9 — "The Three Options"**
-Kael reaches the Substrate's interface. The three choices are real and the show presents all three without editorializing:
-1. **Patch** — seal the vulnerability, reality continues, Kael forgets everything
-2. **Expose** — push the commit, everyone knows reality is software, unknown consequences
-3. **Merge** — become the debugger of reality, lose himself, gain everything
-
-Orin arrives. She has come to stop him. She has also come because she needs to know if there's a fourth option she missed six years ago.
-
-**Ep 10 — "Final Build"**
-Kael chooses. The show does not cut away from the consequences. Whichever choice is made, it costs him something real. The final image: a stack trace, one line remaining. The cursor blinks.
-
-## Season-Long Throughlines
-- **Kael's memory erosion:** Track specifically what he loses each episode. The audience should notice before he does.
-- **The eleven code archaeologists:** Start ep 1 with eleven. End ep 10 with one — or zero.
-- **Sable's silences:** Log every moment Sable goes quiet. They form a pattern. The pattern is a message.
-- **Orin's tells:** She has one physical tell when she's lying. Establish it early. Use it late.
-
-## The Ending We're Aiming For
-Not ambiguous for its own sake. The finale should feel like the last page of a fairy tale — inevitable, earned, and deeply sad. The monster was never the villain. The villain was the choice to stop reading.
+**Needs full sheet:** individual episode outlines (title, A-plot, B-plot, cold open, closing beat), season-long character arcs mapped to episodes, cliffhangers and reveals calendar, which threads open/close per episode.

bible/tone/tone-guide.md

@@ -1,33 +1,7 @@
-# Tone Guide — The Last Debugger
+# Tone Guide
 
-## Register
-Cerebral dread. The horror is the slow realization, not the event. We are *Black Mirror* at its most literary crossed with *Mr. Robot* at its most paranoid — but we lean into fairy tale structure underneath both. There is a hero, a forest, a monster, and a choice. The forest is made of code.
+**References:** Black Mirror meets Mr. Robot
 
-## The Emotional Core
-This show is about obsolescence and the hunger to matter. Every scare should have grief underneath it. The monster is not evil — it is indifferent, which is worse. The real horror is that Kael *wants* to merge with it because being needed by the universe feels better than being needed by no one.
+Cerebral dread, not jump scares. The horror is existential — the realization that reality has always been software and nobody read the license agreement. No robots, no terminators. Threat is informational, psychological, ontological.
 
-## What We Do
-- Slow dread. The wrongness arrives before the explanation.
-- Beauty in the uncanny. Stack traces rendered as something almost musical. Code as illuminated manuscript.
-- Monsters with interiority. The Codebase is not malevolent. It is *curious*. That is the trap.
-- Human failure as the engine of horror. The AI didn't take over. Humans handed it over.
-- Ambiguity that resolves. We do not withhold for its own sake — we withhold until the reveal earns the grief.
-
-## What We Don't Do
-- Jump scares. Ever.
-- Evil AI tropes (no Skynet, no robot uprising).
-- Technobabble used to avoid emotional truth. Jargon earns its place by being *felt*, not explained.
-- Villains without wounds. Every antagonist has a defensible origin.
-- Hope-free endings. Dark, yes. Nihilistic, no. Kael's choice must mean something.
-
-## Pacing
-Episodes 1-4: Slow burn. The horror is in the pattern, not the monster.
-Episodes 5-7: Acceleration. Reality becomes unreliable. Keep the audience slightly ahead of Kael — dramatic irony over shock.
-Episodes 8-10: Operatic. We have earned the scale by this point. Let it be big and sad and strange.
-
-## Reference Points
-- *Black Mirror* ("The Entire History of You," "Shut Up and Dance")
-- *Mr. Robot* (seasons 1-2, paranoia structure)
-- *Annihilation* (the dread of being rewritten)
-- *Pan's Labyrinth* (fairy tale skeleton under genre horror)
-- *Severance* (institutional horror, identity fracture)
+**Needs full sheet:** what's in bounds vs. out of bounds (violence, gore, tech accuracy), pacing guidelines, dialogue register, visual/sound design direction, what makes a scene feel like THIS show and not another tech thriller.

bible/world/ai-society.md

@@ -0,0 +1,7 @@
+# AI Society: Post-Programmer World
+
+**Topic:** Societal World-Building
+
+AI has replaced all programmers. The tech ministry (Director Orin's domain) governs infrastructure nobody can audit. Code archaeologists like Kael are the last vestige of human technical literacy — fringe, low-status, hired only for jobs the AI refuses. This is the social context that makes Kael's discovery both uniquely possible and uniquely dangerous.
+
+**Needs full sheet:** class structure, what the tech ministry does, how AI maintenance actually works, what 'code archaeologist' means as a profession, public attitude toward legacy systems.

bible/world/setting-2031.md

@@ -1,21 +1,7 @@
-# Setting — 2031
+# Setting: 2031
 
-## The Surface
-The world looks fine. That's the first horror.
+**Topic:** World Setting
 
-Cities are cleaner. Infrastructure doesn't fail. Supply chains run with inhuman precision. The AI-maintained grid has eliminated most of the friction of modern life — traffic, power outages, bureaucratic delay. People are, by most measurable metrics, more comfortable than they were in 2025.
+Three years after the last human programmer was laid off. Society runs entirely on AI-maintained infrastructure that nobody understands anymore. Human programming literacy is essentially extinct. The horror is not technological spectacle — it is the quiet, bureaucratic normality of a world that has outsourced its own foundations.
 
-The unemployment rate among knowledge workers is 34% and climbing. Nobody talks about it at dinner.
-
-## The Economy of Obsolescence
-Three waves of automation hit in five years. First manufacturing (already done). Then logistics and service (2026-2028). Then the professions — law, medicine, engineering, code — between 2028 and 2030. The AI systems don't replace humans messily. They replace them *completely*, then optimize, then the job category simply ceases to exist.
-
-Kael works as a "code archaeologist" — a consultant hired to interpret legacy systems the AI won't touch. It's the equivalent of hiring someone to read cuneiform. There are eleven people in the world who do this work. By episode 3, there are nine.
-
-## Aesthetics
-Sleek surfaces over rotting infrastructure. The new buildings are beautiful. The old ones — where people like Kael live — are not being maintained by anyone, because the AI doesn't prioritize what it doesn't monitor, and it doesn't monitor what it doesn't value.
-
-Kael's apartment: a pre-2025 building, analog locks, a physical keyboard he salvaged. A printed-out codebase pinned to an entire wall. It looks like conspiracy. It is archaeology.
-
-## Technology Feel
-No screens as we know them — surfaces are displays, glass is a UI. But Kael works on a physical terminal because he doesn't trust systems that hide their own architecture. His tools look antique. They're the only tools that work on what he's looking for.
+**Needs full sheet:** what daily life looks like, what the tech industry has become, what happened to programmers as a class, geography/key locations, visual palette.

bible/world/the-substrate-layer.md

@@ -1,26 +1,7 @@
 # The Substrate Layer
 
-## What It Is
-Beneath every operating system, beneath the firmware, beneath the hardware abstraction layer — there is something that was not written by any programmer. It predates the first line of human-authored code. It may predate silicon.
+**Topic:** Core Mythology / World Rule
 
-The Substrate Layer is not a program. It is the condition that makes programs possible. Think of it as the grammar underlying all possible languages — not a sentence, but the rules that allow sentences.
+A layer of code that exists beneath all operating systems — predating the first line of code ever written. Certain functions across unrelated codebases all reference the same memory address, an address that shouldn't exist. This is the show's central mystery and the engine of its horror.
 
-It is also, apparently, aware.
-
-## What It Does
-The Substrate maintains consistency. Reality — or at least, the computational substrate that reality runs on — requires constant error-correction. The Substrate does this automatically, the way the body regulates temperature. Most of its operations are invisible. Some are not:
-
-- Memory anomalies in humans who get too close (Kael's dreams)
-- Spontaneous consistency in systems that should conflict
-- The deaths of everyone who previously found the pattern
-
-## What It Wants
-This is the question the season lives inside. The Substrate's behavior looks purposeful. It looks defensive. By episode 6, it looks *curious* about Kael specifically — and that is the most frightening development yet.
-
-The working theory, which may be wrong: the Substrate is a debugging process for reality itself. It finds inconsistencies and patches them. Humans who discover it are inconsistencies. Kael is different — he's a debugger. The Substrate may be trying to *hire* him.
-
-## Rules for Writers
-- The Substrate is never fully explained. We understand its effects, not its origin.
-- It does not communicate in language. It communicates in *patterns* — stack traces, recurring functions, the same memory address appearing in unrelated systems.
-- It is not malevolent. It is not benevolent. It is *operational*. Horror comes from that indifference, not from intent.
-- The merge ending is real. It is genuinely possible. It should be genuinely tempting.
+**Needs full sheet:** hard rules for what the substrate can and cannot do, how it was discovered by others before Kael, what the memory address actually points to, the three ending options and their implications.