bible/characters/director-orin.md

@@ -0,0 +1,7 @@
+# Director Orin
+
+**Role:** Antagonist / Power Broker
+
+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.
+
+**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

@@ -0,0 +1,7 @@
+# Kael Voss
+
+**Role:** Protagonist
+
+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.
+
+**Needs full sheet:** physical description, backstory, psychological profile, arc across all 10 episodes, relationship map.

bible/characters/sable.md

@@ -0,0 +1,7 @@
+# Sable
+
+**Role:** AI Assistant / Possible Antagonist
+
+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.
+
+**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

@@ -0,0 +1,11 @@
+# Season Arc — Season 1 (10 Episodes)
+
+**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.
+
+**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.
+
+**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.
+
+**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.
+
+**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

@@ -0,0 +1,7 @@
+# Tone Guide
+
+**References:** Black Mirror meets Mr. Robot
+
+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.
+
+**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

@@ -0,0 +1,7 @@
+# Setting: 2031
+
+**Topic:** World Setting
+
+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.
+
+**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

@@ -0,0 +1,7 @@
+# The Substrate Layer
+
+**Topic:** Core Mythology / World Rule
+
+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.
+
+**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.