The Glossary

The master doc. The single source of truth for everything in your world — if it's not in the bible, it didn't happen, and if it's in the bible, nothing contradicts it. It's what keeps a world coherent when more than one person is building in it. A bible that nobody actually uses is just a file. A bible built to be legible by your whole team is infrastructure.

The background noise of your world. The history, the myths, the cool stories that make the place feel old and real — the stuff that existed before your story started and will keep existing after it ends. Good lore is an iceberg: most of it stays below the surface, but the audience can feel the weight of it. Bad lore is a Wikipedia article inserted mid-narrative because the writer couldn't help showing their work.

The official, undeniable truth of your story. Everything else is fanfic, speculation, or an alternate timeline — this is the law. In large franchises, canon becomes a political question: which source outranks which, and who has the authority to declare something true. That hierarchy needs to be decided before it's needed, not during the argument it causes.

Making sure your facts line up. If a character loses an arm in chapter 3, they shouldn't be high-fiving anyone in chapter 4. Breaking it accidentally is a mistake. Breaking it repeatedly is a trust problem. Breaking it deliberately, without acknowledgment, is something closer to contempt for your audience.

The whole point. The big idea you're actually trying to say — not the plot, not the setting, the fundamental question the story is structured to ask and answer. Every world element, every character arc, every conflict should be an expression of this. If you can't state it in one sentence, you don't have one yet.

Your world's rules. They don't have to be our world's rules, but they have to be consistent — and they have to feel like they emerged from the world's nature rather than being invented on the fly. Rules that only apply when convenient aren't rules. They're plot devices.

The result of following your own rules without exception. It's what makes the audience say "okay, that makes sense in this world" instead of "wait, that's bullshit." Internal consistency is not the same as realism — a world with dragons can be internally consistent. What matters is that the rules you establish are honored.

The vibe — the emotional register the story operates in. It tells the audience how to feel and how to interpret what they're seeing. A story that can't hold its tone consistently feels amateurish, because it keeps breaking the implicit contract with the audience.

The shelf you put the story on. Fantasy, sci-fi, romance, thriller — genre sets basic expectations before the audience has read a single word. Genre isn't a cage; it's a starting position. Knowing which conventions you're honoring and which you're subverting is the craft.

The elevator pitch. The "what if?" that started everything — the core scenario the story is built to explore. A strong premise contains implicit conflict, implicit stakes, and enough specificity that you can immediately see what kind of story it wants to be.

A group with its own agenda, ideology, and relationship to power. They all want something different — and those competing wants generate conflict. Good factions aren't just political labels; they're expressions of the world's core tensions made structural. Every faction should be able to articulate why they're the heroes of their own story.

The current status quo. A galaxy at war, a kingdom in a golden age, a planet recovering from an apocalypse — this is your starting line. World state is the accumulation of every historical and political decision that led to this moment.

Who's actually in charge, and how did they get that power? Money? Votes? The biggest army? Power structures determine what's possible and what's forbidden — who gets to make decisions, who those decisions affect, and what the consequences are for challenging them.

The old stories the people in your world tell themselves. The creation myth, the legend of the first hero, the cautionary tale about what happens if you go too far. It doesn't have to be true — in fact it's often more interesting if it isn't — but it shapes the culture, the values, and the behavior of everyone living in that world.

The rulebook for your magic. Hard magic has strict, learnable laws — costs and limitations the audience can understand and anticipate. Soft magic is mysterious and atmospheric, implying rules rather than stating them. Neither is better; they serve different narrative purposes.

The money. What's valuable, what's traded, what people do to survive. A fantasy world still needs to know where its bread comes from — who grows it, who distributes it, who taxes it, and what happens to people who can't afford it. Economy is one of the most neglected worldbuilding elements.

How a society governs itself — and by extension, how decisions get made, who gets a voice, and what recourse people have when power acts against them. Political structure is the machinery of the world.

Locations as story elements — not just where things happen, but what the place means and what it does to people. Narrative geography makes place an active participant in the story rather than a backdrop.

A documented list of when things happened. It's your safety net against continuity errors and the most underused tool in worldbuilding. Writers working on a long production without a timeline will contradict themselves — guaranteed.

The fake past you built to make the present make sense. Good constructed history is built backward from the present: given where the world is, what had to happen to produce this? The past explains the present without the present feeling predetermined.

How all your characters relate to each other — a web of allies, enemies, lovers, rivals, and complicated histories. Poke one node and the whole thing shakes. A character ecosystem means nobody exists in isolation; every relationship creates pressure on every other relationship.

How a character changes. They start as a coward and end up brave. Or they go the other way — a tragedy is a character who had the opportunity to change and didn't. An arc that isn't earned feels like a switch was flipped. An arc that's earned feels like it was always inevitable.

The "why" behind a character's actions — what they want, and why they want it badly enough to do what the story requires. Without it, characters feel like they're serving the plot rather than driving it. Motivation doesn't have to be sympathetic, but it has to be legible.

A character's ability to make their own choices and actually affect the plot through those choices. A passive character who just lets things happen to them has no agency — the story is happening to them, not being shaped by them.

The specific flavor of how two characters interact — the bickering partners who secretly respect each other, the mentor-student where the student is surpassing the teacher, the rivals who've been circling each other so long they've become defined by the opposition.

A familiar character template audiences recognize instinctively — The Chosen One, The Wise Old Guide, The Loyal Sidekick. Archetypes are shortcuts that communicate a lot of information quickly. The problem is when a writer uses the template as a substitute for characterization.

Your main character — the one the story follows, the one whose journey defines the narrative. The protagonist is not necessarily the hero, the most powerful, or even the most likeable. They're the character whose perspective the audience inhabits.

The one standing in the protagonist's way — the primary source of opposition. Not always a villain, not always even a person. The antagonist is defined by their relationship to the protagonist's goal, not by their moral alignment.

A group where no single character is definitively the protagonist — the story belongs to the team. Ensemble storytelling is harder than single-protagonist work because every character needs enough depth to carry their own scenes.

The way a specific character talks — word choice, sentence rhythm, the things they notice, the things they don't. Voice is how you make a character feel like a complete person who existed before the story started.

The underlying rules of how the story is told — especially in interactive media. Is it linear? Branching? Open-world with emergent stories? The narrative system isn't the story itself; it's the engine that generates and delivers it.

The blueprint of your plot — acts, chapters, turning points. Architecture is the discipline of understanding not just what happens but when it happens and why that timing matters. A story with perfect events in the wrong order is still a broken story.

Just the stuff that happens. Event A causes Event B causes Event C. Plot is often confused with story, but they're different things — story is the emotional experience; plot is the mechanism that creates it.

What's at risk? What happens if the protagonist fails? If the answer is "not much," your story is boring. Stakes don't have to be world-ending to be compelling. A character risking their last meaningful relationship is higher stakes than saving the universe from a villain nobody cares about.

The engine of plot. Conflict is not just fighting — it's any situation where competing desires, needs, or forces are in opposition. The richest stories have conflict operating on multiple levels simultaneously: external mirrors internal.

That feeling in the pit of your stomach. Tension is not the same as conflict — conflict is a state, tension is a feeling. You create it by making the audience care about an outcome and then making them uncertain whether they'll get it.

The speed of the story — how quickly events move, how long you linger on a moment, how much breathing room exists between peaks. A story at maximum speed all the time is exhausting. Pacing is rhythm. The quiet moment makes the loud one matter.

A single, small story moment — a decision, a revelation, a shift in emotional state, a change in power dynamic. Beats are the building blocks of scenes; scenes are the building blocks of sequences.

Planting a promise early on that will be fulfilled later. Every setup creates an expectation, and every expectation is either honored or consciously subverted. Ignoring a setup you've planted is not a choice — it's a mistake the audience will notice.

The moment a promise is fulfilled. Payoff is what the audience has been waiting for, and the satisfaction of it is proportional to how well the setup was done and how long the tension was sustained.

The stakes keep getting higher. The enemy gets stronger. The personal cost increases. Escalation is the engine of sustained narrative momentum. But it has a ceiling — a story that escalates without limit eventually reaches a point where nothing matters because the scale has left the human behind.

Hints at what's to come. Foreshadowing is what makes a story feel inevitable in retrospect rather than arbitrary. It's also one of the clearest markers of intentional craft — a story that's been planned rather than improvised.

The feeling that the player's choices actually matter — not the illusion of choice, but the genuine article, where decisions have consequences that change the world. If all choices lead to the same outcome, you haven't built agency; you've built the perception of it, which is worse.

How you present choices to the player — the design of the choice itself, not just its consequences. The architecture shapes how the player experiences making the decision, which shapes what the choice means emotionally.

A story that splits into different paths based on player choices. Branching is expensive because you're writing multiple versions of reality, most of which the player will never see. The design challenge is making every branch feel meaningful.

The behind-the-scenes logic that tracks player choices and changes the world accordingly. A well-designed consequence system creates the feeling that the world remembers — and that memory makes choices feel significant.

The branching structure of a conversation — what you say determines what they say next. Every node is simultaneously a creative choice and a systems decision. The craft is making every branch feel like a real response from a real person.

A flag in the game's code that tracks something the player did. PlayerKilledMerchant = TRUE. PlayerSavedCity = FALSE. That flag can reshape the entire world later. World state variables are the mechanism behind "the world remembers."

Stories the game didn't script but the player created through interaction with the systems. Unplanned, unrepeatable, and often more personally meaningful than anything scripted — because the player made it.

When the gameplay and the story are saying the same thing — when what you're doing mechanically is an expression of what the story is about thematically. When mechanics and narrative align, games achieve something no other medium can.

When the gameplay and the story are at war. A cutscene where the hero says "I won't kill," immediately followed by a combat section where you mow down fifty people. Dissonance doesn't just feel inconsistent — it makes the story feel dishonest.

A gameplay mechanic that is the story — where the act of playing is the act of experiencing the narrative, inseparably. A narrative mechanic doesn't support the story; it is the story.

Telling one big story across multiple platforms — the main plot in the films, a side character's backstory in a comic, a prequel in a game. Done well, each platform adds something unique that couldn't exist elsewhere. Done badly, it's just redundant content that doesn't justify its own existence.

Your universe as a commercial and creative asset — the characters, the stories, the world, the brand identity — the thing you can license, sell, and build on. Understanding your IP means understanding not just what you've created but what makes it uniquely valuable and defensible.

Turning a story from one medium into another. It's a translation, not a photocopy. Each medium has different strengths and constraints, and a faithful adaptation honors the spirit and core of the original while making decisions specific to the new medium.

The ranked ordering of which sources are most "true" when they contradict each other. This hierarchy needs to be declared and documented before it's needed — because when contradictions appear (and they will), someone needs to make an authoritative call.

A story that branches off the main one, focusing on a secondary character, location, or time period the original couldn't fully explore. A good spinoff earns its existence by doing something the original couldn't. A bad spinoff is just the original with the interesting parts removed.

All the supplementary material that fills in the gaps — comics, novels, games, animated series. A gift to invested fans and completely ignorable by casual ones. The problem arises when the main property starts requiring engagement with expanded universe material to follow its own plot.

A fresh start that still nods to the original — new story, same world, often with original characters in legacy roles. It says: we respect what came before, but we're starting a new story new audiences can enter without a history degree.

Throwing everything out and starting from zero. The only things that carry over are the brand name and the foundational premise. It's the right call when accumulated continuity has become so tangled it's actively preventing good stories.

Changing past facts to serve a new story. Sometimes brilliant — a recontextualization that makes everything prior richer. Sometimes lazy — an erasure of audience investment without doing the work. The difference is whether the retcon serves the story or the story is being bent to serve the retcon's convenience.

Officially made, but not part of the real timeline — the "what if?" zone. Fun, sometimes brilliant, but it doesn't count. The trouble starts when non-canon material becomes beloved enough that fans resist its non-canon status.

The big book of plans for a game — story, mechanics, art direction, systems, all in one place. A living design document evolves throughout production. A frozen one becomes outdated. The best ones are detailed enough to solve problems before they become building problems.

The world bible built specifically for a TV show's writers' room — where multiple writers on different episodes need to stay in the same creative universe. It covers character biographies, world rules, tone guidelines, and backstory that might never appear on screen but shapes how everyone behaves.

A group of writers throwing out ideas, breaking stories, and building plots together — collaborative chaos with structure underneath it. The engine of episodic television and increasingly of games. It distributes creative load and generates ideas no single writer would reach alone.

The intense process of taking a story idea apart and rebuilding it with solid structure. You start with a concept and end with an outline. Story breaking is where the fun idea meets the hard questions: What's the conflict? Where does the protagonist change?

The step-by-step plan before you write. It's the map — the document that tells you where you're going before you write the territory. A good outline solves story problems before they become writing problems.

A short prose summary of the whole story — written to sell the vibe and the plot before a full script exists. It answers: what happens, to whom, why it matters, and why this story is worth making.

The sales brochure for your story idea. A pitch document has one job: create enough belief in the project that the person reading it wants to fund it, greenlight it, or sign on.

The moment a studio, publisher, or network says "go make it" and attaches the budget. Greenlight is the transition from development to production — from the project being a possibility to being a commitment.

Where good ideas go to die. A project stuck in limbo — endlessly rewritten, passed between teams, greenlighted then un-greenlighted, stripped of its original vision through accumulated compromise.

The document that grows throughout production — tracking everything: assets, lore, character designs, approved decisions, continuity notes. It starts as a world bible and expands into a record of every creative decision made during the project.

Passing your world to a new team — the most dangerous moment for lore drift and creative misinterpretation. A handoff that's just a document delivery is a recipe for problems; the new team can read the words without understanding the reasoning.

When the facts of your world slowly change because writers forget or don't check the bible — a slow erosion of truth. Lore drift is insidious because no single change is obviously wrong. It's only when you zoom out that you see the world has become a different world.

A simple factual mistake — a character's scar moves between scenes, a weapon changes color. Continuity errors break immersion because they remind the audience they're consuming a constructed thing — someone forgot to check.

A logical gap big enough to drive a truck through — a character knows something they couldn't possibly know, a problem is solved by pure luck with no setup. Plot holes reveal the writer's hand: someone needed the story to go here and didn't do the work to earn it.

A piece of your world or plot that everything else rests on. Remove it and the whole story collapses. Load-bearing elements need to be identified early and handled carefully — they can be developed, complicated, and challenged, but they can't be casually discarded.

When you have too much stuff — too many characters, too much history, too many subplots — and the core story gets lost in the noise. The cure is asking, for every element: what does this do that nothing else already does?

Poking and prodding your world to see where it breaks. Ask "what if?" questions until you find a logical flaw. Finding these breaks before production is an investment. Finding them after production is a crisis.

Every single thing should do more than one job. A line of dialogue that reveals character, advances the plot, and establishes tone simultaneously is doing three things at once. A scene that only does one thing is probably too long.

The feeling that your world is deep and lived-in — that there's history beyond the page, stories happening off-screen, texture that extends past the edges of what the audience directly experiences. Show 10%, imply the other 90%.

The power of what you don't say or show — the gaps and silences that let the audience's imagination do the work. Negative space is what separates confident storytelling from insecure storytelling.

When the audience forgets they're reading a book or playing a game — they're just in the world. Immersion is fragile. A continuity error breaks it. A tonal inconsistency breaks it. The goal is not to hide the art completely — it's to make the art good enough that the audience stops looking for the seams.

The audience's agreement to accept the impossible — dragons, FTL travel, magic — as long as you play fair with everything else. It's a transaction. The audience gives it when the world earns it through consistency.

The audience's belief that you, the creator, know what you're doing and that their investment will be honored. Earn it with good stories. Lose it with lazy ones. The worst thing you can do isn't making a bad story — it's making a story that betrays the investment people made in your previous ones.

The unspoken agreement about what kind of story this is and what rules it operates by. Breaking the narrative contract isn't subverting expectations — it's betraying the audience's trust in the premise they agreed to engage with.

Doing the opposite of what the audience expects in a way that feels earned rather than arbitrary. The best subversions feel inevitable in retrospect. The worst feel random or spiteful — the story broke its promises not to say something new but just to be unpredictable.

The one big conflict that drives everything — not between specific characters but between ideas, values, or forces that every character and faction has a position on. Core tension is the engine under everything else; it's what the world is arguing about, expressed through story.

The system of ideas your story is built on — the cluster of interconnected themes that every scene, character, and conflict is designed to explore. A thematic framework is not a list of themes; it's the specific way they relate to each other.