01 · Motivation

Why We Started Here

The central promise of Book Mode is that the same generated story can be run by different groups of players · perhaps months or years apart · and still deliver a meaningful, surprising experience. That is a hard problem. Most authored content, when played twice by people who've compared notes, collapses into a guided tour of already-known beats. The tension evaporates. The sense of discovery is gone. For Book Mode to be commercially viable, it cannot be a single-use experience. People will share stories. Players will replay with different characters. The engine needs to produce content that can survive that exposure · and still feel alive.

Before designing any schema, we needed to know whether this was even solvable through structure alone · whether a pre-generated story could be made replay-resistant through authorial discipline, or whether it required algorithmic variation at generation time. The answer to that question would determine the entire architecture of Book Mode.

The Enemy Within (TEW) is the answer. Published by Games Workshop between 1986 and 1989, revised and expanded across decades, and now in a Director's Cut edition that Graeme Davis · one of its original authors · spent three decades refining, TEW is not merely considered a great campaign book. It is the campaign book. In the tabletop RPG community, arguments about the greatest adventure ever written converge on TEW with unusual regularity. Groups have been running it since Reagan was in office. New players who know nothing about Warhammer pick it up and find it works. Groups who've run it before run it again · differently. That longevity is structural, not incidental. Understanding precisely how it achieves that is the whole point of this research.

The question driving this research: Can a pre-authored story with a known ending genuinely surprise a player who has already seen that ending? TEW says yes · and then shows exactly how. The mechanism is what we've named Fixed Spine, Variable Flesh.

02 · Campaign Architecture

The Structural Secret of The Enemy Within

TEW is a picaresque narrative · its characters are deliberately small people swept into events far larger than themselves, moving through a world that doesn't care whether they show up. The protagonists begin as ordinary travellers: hired bodyguards, petty merchants, wandering scholars. By the time the campaign concludes across its five volumes, they have penetrated the highest levels of conspiracy in the Old World. But the world never paused to wait for them. That restlessness, that sense of a plot in motion regardless of the players' attention, is baked into TEW's structure from the first page.

The five volumes · Enemy in Shadows, Death on the Reik, Power Behind the Throne, The Horned Rat, and Empire in Ruins · are not chapters in a single linear story. They are locations. Each book is a place: a city, a river, a carnival, a frontier. The players move through these places, and the conspiracy is what they find threaded through all of them, connecting everything they encounter into a single coherent pattern that only becomes legible late in the campaign.

That coherence is maintained by a conspiracy spine that exists entirely independently of player action. The Purple Hand cult is plotting. Karl-Heinz Wasmeier, Law Lord of Middenheim, is using blackmail, murder, and political manipulation to consolidate power for forces of Chaos. The Skaven are moving beneath the city. These facts are true whether the players discover them or not. They would be true if no players ever sat down at the table. The GM knows them. The NPCs act accordingly. The world shows their effects. The players are not discovering a story that is written for them · they are discovering a history that already exists.

Core insight: The campaign feels alive not because the players are the most important people in the world, but because the world already has important people in it · and those people are busy. The conspiracy is not waiting. The players are catching up to something already in progress.

This is what makes TEW structurally different from most adventure design. The typical campaign book arranges the story around the players: they arrive, the villain reacts, the investigation proceeds at their pace, the climax happens when they are ready. TEW inverts this. The conspiracy proceeds at its own pace. Players who move slowly find that events have overtaken them. Players who rush find they've stumbled into something before they understood it. Neither experience is wrong · both are consequences of the world having its own momentum.

The campaign scales across five volumes without losing this coherence because the spine · the overarching Chaos conspiracy · touches every location. When players are bouncing down the Reik on a river barge, the conspiracy is there in the passengers sharing their boat and the cargo in the hold. When they reach Middenheim for the carnival, the conspiracy is in the tax laws, the Guild structure, the carnival performers, and the legal system simultaneously. Nothing is decorative. Every location element connects upward to the spine.

5Campaign Volumes
28Core NPCs in PBtT Alone
33Tracked Events in PBtT
16Key Locations in PBtT
40+Years of Replay
03 · Core Design Principle

Fixed Spine, Variable Flesh · In Detail

The distinction that makes TEW replayable can be stated plainly: the conspiracy is a fact, not an experience. The players' discovery of the conspiracy is the experience. These two things are entirely separable. The first · what is true in the world · is the spine. The second · how any particular group of players comes to understand it · is the flesh. TEW holds the spine constant across every playthrough. It surrenders the flesh entirely to the unpredictable intersection of player choices, GM improvisation, dice, and circumstance.

The result is that two groups can run Power Behind the Throne · the third volume, set in Middenheim during carnival week · and have almost no overlap in their actual experience. One group might make allies of the city watch and work through official channels, slowly learning that the institutions they trusted are compromised. Another might go directly underground, find the Skaven tunnels first, and approach the surface conspiracy from below with information the first group never had. A third might antagonize half the city, burn bridges with every faction, and still stumble into the truth through a drunken NPC in a tavern they visited out of boredom. All three groups will have discovered the same conspiracy. None of their stories are the same.

The spine is the truth. The flesh is one particular group's path to that truth. You can regenerate the flesh endlessly. The spine is what ensures the truth is always worth reaching.

What Is Fixed · The Spine

The conspiracy itself: who is behind it, what they want, when the timeline escalates, and what happens if players fail to stop it. The major characters and their true agendas · not their public faces, but the secret role each plays in the conspiracy. The climax and its conditions: the ritual will be attempted, the specific person is pulling the strings, the specific threat is real. The world change: what is permanently different in the Empire once the campaign concludes, regardless of outcome. These facts cannot change between playthroughs without destroying the campaign's identity.

What Varies · The Flesh

Which clues the players find, in what order, and through what means. Which NPCs they befriend, offend, or ignore entirely. Which side quests they pursue and which they miss. Which red herrings they chase and which they see through. Which version of the truth they've assembled by the time they reach the climax · they may arrive with the full picture, or with half the puzzle, or with entirely wrong assumptions that force a different approach to the finale. The Director's Cut adds "Grognard Boxes" · alternative entry points and NPC variants specifically designed to surprise players who've run it before.

For the Narrative Engine, this distinction maps directly onto a generative question: what must the arc generator produce once and preserve forever, versus what the rendering layer can vary on every pass? The spine is generated by Sonnet in the Arc Generation phase and locked. The flesh · the specific clue paths, the precise sequence of discovery, which NPCs the player encounters first · is where Haiku has latitude. This is not just a design preference. It is what makes Book Mode economically viable: you generate the spine once, and it serves hundreds of playthroughs without expensive regeneration.

Engine implication: The Arc schema's spine fields (premise, inciting_incident, climax, resolution, world_change) are Sonnet outputs generated once and marked immutable. The clue_nodes array, the entity_references on beats, and the optional_revelations fields are where the flesh lives · these can be varied algorithmically per playthrough without touching the spine at all.

04 · Character Design

The NPC Web Model

TEW's NPC design is not a list of characters · it is a web of contradictions. Every significant NPC in the campaign has at minimum two layers: what they appear to be, and what they actually are. The apparent layer is what players observe on first contact. The actual layer is what investigation, persuasion, or accident reveals. The relationship between these layers is not random · it is always in service of the spine. Every secret connects upward to the conspiracy, even if the connection is indirect.

Power Behind the Throne · universally considered TEW's masterwork volume · makes this web explicit. Its core adversary, Karl-Heinz Wasmeier, presents publicly as the Law Lord of Middenheim: a stern but legitimate authority, someone players might initially want as an ally. His secret is that he is simultaneously the Magister Magistri of the Purple Hand cult, using his legal position to protect cultists, eliminate threats, and advance a Chaos agenda beneath the veneer of civic order. The public face is not just a cover · it is actively part of the conspiracy. His legal authority is the mechanism of his evil.

This model repeats at every level of the NPC web. A carnival performer who seems to be a harmless entertainer is in fact a cult spy. A merchant complaining about new taxes is genuinely suffering from policies designed to destabilize the city · and his grievance, real as it is, is being manipulated by forces he doesn't know exist. A guard captain who obstructs the players is not a villain · he's a functionary doing his job · but his job protects a corrupt system, and whether players treat him as an enemy or a potential ally changes their path through the investigation.

In TEW, the question is never "who is the villain?" · the players know that eventually. The question is "who else is?" · because the conspiracy is the entire social fabric, and almost everyone is entangled in it, wittingly or not.

What makes this web navigable · and what makes it feel like a coherent world rather than an overwhelming tangle · is that TEW provides the GM with a diagrammatic relationship map and nine pages of NPC usage guidance for Power Behind the Throne alone. This is the analog equivalent of what our Entity schema must produce at generation time: a structured representation of every NPC's public face, secret, connections, and agenda that the rendering layer can query against when generating dialogue or interaction beats.

The "Layers of Truth" Structure

TEW structures its revelations in concentric rings of truth. The outermost ring · what everyone knows · is freely available and never requires investigation. The middle ring · what careful observation reveals · requires the players to be paying attention and asking the right questions. The inner ring · the actual conspiracy · requires deliberate investigation and usually multiple clue paths converging on the same conclusion.

This is not merely a pacing device. It means that players at different engagement levels all get value from the campaign. A player who stays at the surface experiences a rich political drama. A player who digs deeper finds the occult horror underneath. A player who goes all the way to the core understands why the whole world feels wrong in the way it does. No one is blocked. No one gets the full picture without working for it.

For the engine, this maps directly onto the Entity schema's distinction between public_description/public_role and secret/ hidden_connections. The rendering layer knows which layer it is drawing from · and that knowledge constrains what any particular NPC can say in any particular conversation.

Concrete NPC example · the Merchant Guild Factor: Public face: a legitimate trade official, frustrated by new import taxes, willing to share economic gossip to anyone who buys him a drink. Useful to players as a source of information about city economics. Secret: his guild is a Purple Hand front and he launders cult funds through trade invoices. Hidden connection: direct subordinate of Wasmeier. The players may never learn his secret. But if they do, every economic clue they gathered from him gains retroactive meaning · and the path to Wasmeier shortens dramatically.

The NPC web model also solves a specific generation problem: it prevents NPCs from feeling interchangeable. When every NPC has a defined agenda · not just a personality · their behavior in any given scene can be derived rather than invented. The Guild Factor doesn't want the players digging too deep into guild finances. That agenda shapes every interaction he has with them, regardless of what the players ask. The rendering layer doesn't need to be told how he reacts to every possible player input · it needs to know his agenda, and then it can derive the reaction.

05 · The World Without Players

Event Timelines and Passive Momentum

One of TEW's most quietly radical design decisions is that every significant location includes a calendar of events that proceeds regardless of player action. Bogenhafen has its Schaffenfest. Middenheim has its carnival week. The cult has its meeting schedule. The ritual has its window. These are not encounter prompts waiting for players to trigger them · they are facts about the world that exist in time, and the players are moving through that time whether they engage or not.

A typical event timeline entry reads something like: Day 1 · the cult meets in the Merchant Guild cellars at midnight. Day 3 · the merchant who knows too much is found dead. Day 5 · a prominent city official disappears. Day 7 · the ritual begins. Day 10 · the ritual concludes unless interrupted. Players who arrive at the start of the carnival have ten days to unravel the conspiracy. Players who waste three days pursuing a red herring arrive to find the merchant already dead · and the pressure has escalated. Players who ignore every signal find themselves present at a ritual they had no idea was coming.

Why the Passive Timeline Creates Better Stories Than Triggered Events

The standard adventure design approach gives the GM a series of events that trigger when players reach a certain point or perform a certain action. Nothing happens until the players initiate it. This creates a fundamentally safe experience: the world waits. The consequences of inaction are never felt, because inaction never causes the story to progress without the players.

TEW's timeline design creates the opposite dynamic. The world is indifferent to whether the players are ready. The conspiracy will attempt the ritual on Day 7 whether the players know about it or not. This indifference is what makes the world feel real. Real conspiracies don't pause because the investigators haven't gotten the memo. The sense of urgency TEW generates is not manufactured by artificial countdown timers · it comes from the credible feeling that something is happening, right now, in a place you're not.

For a narrative engine, this is the difference between a story that happens to players and a story that players happen to. Both produce narrative. Only one produces genuine tension.

There is a second function that passive timelines serve beyond dramatic tension: they provide narrative content for the rendering layer even when players are doing nothing. If the cult meets on Day 1 whether players attend or not, that meeting creates a feed item, a board notice, a rumour in the chat channel. The world is generating signal. Players who are paying attention will notice the pattern. Players who aren't will still experience a world in motion, even if they don't understand what is moving.

This is the origin of what the engine calls the passive timeline in the Arc schema: not merely a design principle borrowed from TEW, but a structural requirement that every arc define what the world looks like at each moment if the players are absent. In the Arc schema, the passive_timeline array entries each carry a visible_signs field the observable surface trace of an event that players might notice without knowing what caused it. A closed warehouse. An empty chair at the merchant's usual table. A watch patrol that's been doubled without explanation. These are the signs of a timeline advancing, rendered in the appropriate delivery channel, whether or not any player is watching.

Engine implication: The Arc schema's passive_timeline entries and the fronts / clocks system both derive from TEW's event timeline model. A front advances on its own trigger conditions, not on player engagement. The advance_trigger field on each front step can be time-based ("48 hours after arc start"), event-based ("after the cult meeting beat completes"), or threshold-based ("if no player has visited the Merchant Guild within 24 hours"). All three modes originate in TEW's calendar logic.

06 · Delivery Channel Theory

Handouts as Diegetic Content

TEW is famous for its physical handouts · and the fame is deserved, because the handouts represent a design principle that most campaign books get entirely wrong. A TEW handout is not a summary of information the GM would otherwise narrate. It is a document that exists in the world of the campaign. A wanted poster is not a convenient information delivery mechanism. It is an actual wanted poster · written in the vernacular of an Imperial magistrate, laid out with the typography of an eighteenth-century broadsheet, including institutional boilerplate that no narrator would ever include because narrators naturally strip the noise to signal. The noise is the point.

When players receive a TEW handout · an intercepted letter from a Purple Hand cultist, a legal summons from the Middenheim court, a hand-drawn map with annotations in a stranger's handwriting · they are not receiving information. They are receiving an artifact. The artifact carries information, yes, but it also carries context: who wrote this, in what circumstances, with what expectations of the reader. A cultist's letter doesn't announce "I am a cultist conspiring against the Empire." It uses the language of ordinary correspondence to discuss ordinary business, and the conspiracy is visible in the gaps, the euphemisms, and the unexplained references to people and places the players might eventually recognise.

Diegetic vs. Extradiegetic Rendering

In narrative theory, diegetic content exists within the story world. Extradiegetic content exists outside it · the narrator's voice, the chapter summary, the "read-aloud text" box that sounds like a storyteller describing a scene. TEW uses both, but its power lies in knowing precisely when to use each.

Extradiegetic narration tells players what they observe. It is efficient and controlled. But players experience it as information being given to them, which creates a passive relationship with the content. Diegetic content asks players to interpret a thing that exists in the world. A bulletin board notice, a threatening letter, an intercepted message · these are things players discover rather than are told. The act of discovery changes the emotional register of the information entirely. Players who decode a cultist's euphemisms feel clever. Players who are told "this person is a cultist" feel managed.

The rendering problem in EV2090 is almost entirely a diegetic failure. A bulletin board post that sounds like a narrator is extradiegetic content in a diegetic container. The channel says "bulletin board." The voice says "narrator." The player's brain detects the mismatch before it can articulate it. The content feels sloppy even if the information is perfectly accurate.

TEW's handout design is, in effect, a delivery channel specification document built into the adventure itself. When TEW defines what a wanted poster looks like, it is not just providing props · it is establishing a grammar. A wanted poster uses declarative sentences. It includes a physical description, a named offence, a reward amount, and an authority signature. It does not editorialize. It does not explain context. It assumes the reader knows what a wanted poster is for. When the Narrative Engine generates a board notice, every one of these attributes should be present · not because someone wrote a rule that says "include reward amounts," but because the board notice is a wanted poster, and wanted posters have a form that exists in the world for functional reasons.

This is what the engine means by delivery channel rendering. A feed broadcast doesn't sound like a wanted poster. A chat message doesn't sound like a legal summons. Each channel has a form that exists in the world for its own functional reasons, and that form is not optional flavor · it is the mechanism by which the content lands as real rather than narrated.

Engine implication: Every delivery channel in the engine should have a grammar specification analogous to TEW's physical handout design. The rendering_context.format field on each beat is not just a label ("bulletin board") · it is a pointer to a specific formal grammar that Haiku uses as a constraint. That grammar includes institutional boilerplate, sentence structure norms, and explicit anti-patterns (e.g., "a board notice never summarises the plot; it announces a single actionable fact"). The channel specification is where TEW's handout design lives in the engine architecture.

07 · Key Findings

What This Research Revealed

Surprise 1: The Investigation Structure Is Node-Based, Not Linear

We expected TEW to be a carefully sequenced linear investigation · clue A leads to clue B leads to confrontation. It is not. TEW uses what modern game design calls node-based scenario design: a web of locations, NPCs, and clue fragments that players can visit in almost any order. Any three nodes, converged upon, yield enough information to reach the next major conclusion. This is the Three-Clue Rule in structural form: the campaign's investigation is robust not because it leads players by the nose, but because there are so many independent paths to every critical revelation that players effectively cannot miss the important ones.

For the engine, this means the clue node network in an arc is not a sequence · it is a graph. The Sonnet choreography phase must generate a graph of clue nodes with enough cross-connections that any three-node subset provides adequate forward momentum. This is a more complex generation constraint than a linear sequence, but it is what produces the "living world" feeling that TEW achieves.

Surprise 2: The NPCs Have Schedules

TEW's NPCs are not available whenever players want them. They have daily routines. The Guild Factor is at the exchange until noon, at his usual tavern from noon to two, and unreachable in the afternoons. The watch captain does his rounds at specific hours. The cult messenger passes through the market district on specific days. These schedules serve a design function that initially seems like administrative overhead: they prevent the players from simply interrogating every NPC in sequence.

But the schedules do something deeper. They force players to plan · to observe patterns, to choose which NPC to reach at what time, to be at the right place at the right moment. This is the mechanic that produces the sensation of infiltrating a living conspiracy rather than working through a list of encounters. For the engine, NPC schedule data is part of the Entity model · not just where an NPC is, but when they're there, and what routine events create natural observation and interception opportunities.

Surprise 3: The Moral Complexity Is Structural, Not Incidental

TEW is not a campaign about fighting evil · it is a campaign about recognising it in the familiar. The conspiracy does not consist of monsters visibly identifiable as threats. It consists of a law lord, a guild master, a carnival performer, a tax collector. People the players encounter as ordinary citizens of the Empire, whose ordinary activities serve as cover for something that threatens to unravel the Empire's entire social structure.

This moral complexity is not a narrative flourish added on top of the structure · it is produced by the structure. Because every NPC has a public face and a secret, the space of possible moral states includes people who appear threatening but are innocent, and people who appear benign but are dangerous. Players cannot assume alignment from appearance. This uncertainty, maintained systematically across the entire NPC web, is what creates the paranoid atmosphere that TEW is famous for. For the engine, this is an argument for ensuring that the NPC generation prompt explicitly requires a gap between public_role and secret · not as a mandatory twist, but as a design space that cannot be left empty.

Surprise 4: Replayability Requires Authorial Restraint

The Director's Cut edition, which Graeme Davis spent three decades revising, is notable not for how much it adds · but for how carefully it identifies and removes content that inadvertently constrained the flesh. The original campaign occasionally specified how players would discover certain clues, locking a discovery mechanism that varied GM ingenuity would naturally have expanded. The Director's Cut converts these locked paths into open nodes: here is the information, here are multiple ways it might become available, choose based on what fits your table. The editorial impulse is toward openness at the flesh level and solidity at the spine level · and the discipline required to know which is which is the hardest part of replayable design.

For the engine, this means the required_revelations and optional_revelations distinction on the Beat schema is not bureaucratic · it is the primary quality control for replayability. Required revelations define the spine at the beat level. Optional revelations are flesh. Sonnet must be instructed to generate these as distinct categories, not as a single undifferentiated list of content.

08 · Design Decisions

How TEW Shapes the Engine

The research produced six concrete design decisions that are now locked into the engine's architecture. Each one maps a TEW mechanism to a specific schema field or generation constraint.

Decision 1 · Spine fields are locked at generation time. The Arc schema's premise, climax, resolution, and world_change fields are generated by Sonnet in the Arc Generation phase and are not modifiable by any subsequent rendering or consequence processing step. Book Mode treats these as immutable. Sandbox Mode can alter them only through an explicit spine renegotiation pass · a deliberate, expensive Sonnet call · not through incremental drift.

Decision 2 · Every NPC must have a gap between public and secret. The Entity schema's public_role and secret fields are both required · not optional. The generation prompt for Arc characters explicitly requires that the secret connect upward to the arc's spine, directly or through one intermediary. An NPC whose secret is merely a personal quirk unconnected to the conspiracy is not a TEW-style NPC · it is decoration.

Decision 3 · Passive timelines are required, not optional. Every arc · Book Mode and Sandbox Mode · must include a passive_timeline array with at minimum three entries: one at arc start, one at the midpoint, and one at the climax window. Each entry requires both an event (what actually happens) and a visible_signs field (what a player could observe). The engine uses these to generate ambient channel content even when no player-triggered beat is active.

Decision 4 · Clue nodes are a graph, not a sequence. The Arc schema's clue_nodes array is not ordered. Each clue node has a leads_to array of other node IDs. Sonnet is instructed to generate clue node graphs where any single critical revelation has at least three independent approach paths. The Three-Clue Rule is enforced at arc generation time, not as a post-hoc audit.

Decision 5 · Delivery channels have formal grammars, not just labels. The rendering_context block on each Beat must include an anti_patterns array that specifies what the channel must never sound like, derived from the channel's real-world formal grammar. "A board notice never summarises the arc premise." "A broadcast never uses first-person voice." These constraints encode TEW's implicit handout grammar explicitly, so Haiku is constrained by channel form, not just told what channel it is.

Decision 6 · Required and optional revelations are distinct fields. The Beat schema separates required_revelations (spine-level information the player must receive for the arc to be coherent) from optional_revelations (flesh-level information that enriches the experience but is not load-bearing). Haiku can vary how it presents optional revelations across playthroughs. Required revelations must appear in the rendered beat regardless of variation. This is the TEW editorial discipline encoded as a schema constraint.

09 · Connections

Connections to Other Research

Research 01 · D&D Module Structure

Two Layers of the Same NPC Model

D&D defines who an NPC is as a person (trait, ideal, bond, flaw, agenda). TEW defines how that person connects to the conspiracy (public face, secret, hidden web). Both are required in the Entity schema: the personality block comes from D&D; the hidden_connections and secret fields come from TEW.

Research 04 · Improv DM Techniques

Two Solutions to the Same Problem

TEW's authored event calendar and Apocalypse World's Fronts/Clocks solve the same problem: how does the world move forward without player initiative? TEW uses a pre-written schedule (Book Mode). Fronts use a generated countdown (Sandbox Mode). The distinction between the two passive timeline models is, at its root, the TEW/AW distinction.

Research 05 · Procedural Narrative AI

The Spine as a Coherence Constraint

AI narrative research confirms that pure generation without constraints produces coherence decay. TEW's fixed spine is a constraint system: the conspiracy is a set of fixed facts every generated beat must stay consistent with. The Arc Audit phase in the engine pipeline exists specifically to defend the spine against generative drift.

Research 06 · EV2090 Code Analysis

A Diagnostic Tool for the Gaps

The eight structural gaps in EV2090 map almost one-to-one onto failures to implement TEW principles. No player agency = no functional passive timeline. Stateless rendering = no NPC agendas. Disconnected arcs and bounties = no shared NPC web. TEW is not just inspiration — it is a precise diagnostic for what is missing.

The deepest lesson of TEW for the Narrative Engine is a philosophical one: a great campaign book is not a story written for players. It is a history that players discover. The distinction sounds subtle, but it determines everything about how the engine must generate arcs · not as narrative sequences designed to be experienced, but as world states with their own internal logic that will inevitably be encountered. The engine's job is not to write stories. It is to instantiate histories that become stories when players walk through them.