The Rules Behind the World

Every long-running fictional world eventually contradicts itself. A detail established in chapter three conflicts with something implied in chapter twelve. A species' biology shifts between stories. A character's history quietly rewrites itself. The longer the project runs, the more stories and contributors and years it accumulates, the more the contradictions pile up.

The standard advice is to keep better notes. Build a bible. Write everything down. And that advice is good, as far as it goes. A reference document that records what's true in your world is essential. But it doesn't solve the deeper problem, because the deeper problem isn't about record-keeping.

It's about process.

A world bible tells you what is true. It doesn't tell you how things became true, how they can change, or what to do when two truths conflict. It records the current state of the world but says nothing about the process that produces and maintains that state. When contradictions emerge (and they will), the bible can identify them but can't resolve them. Resolution requires answering questions the bible was never designed to ask. Which version takes precedence? Who decides? How much other content breaks if we change this? What's settled and what's still open?

These are governance questions. And every shared fictional world has governance, whether it's made it explicit or not.

The implicit constitution

Think about any creative project that involves building within a shared world. It might be a solo novelist writing a series. A writing room developing a television show. A tabletop RPG campaign that's been running for years. An open world that invites fan fiction. In every case, the participants are operating under a set of implicit rules: not the physics of the world or the history of its people, but the meta-rules about how creative decisions get made, maintained, and revised.

Some of those rules are about authority. Who gets to establish new facts about the world? Who resolves disagreements? For a solo author, the answer seems obvious: you do. But a solo author working across a long series is collaborating with their past and future selves, and anyone who has tried to change something established three books ago knows that "I'm the only author" doesn't make the change cost-free.

Some of the rules are about stability. Which parts of the world can be freely revised, and which are load-bearing, built upon by so much subsequent work that changing them sends cracks through everything? A species' fundamental biology, established in the first story and referenced in every story since, is not the same kind of creative decision as a character detail introduced last week. They carry different weights. They should be governed differently.

Some of the rules are about process. When new creative work introduces something that touches the shared foundations, a story that casually establishes a fact about the world's physics or a session that invents a piece of deep history, how does that get noticed, assessed, and either accepted into the shared canon or flagged for discussion?

Every project answers these questions, one way or another. Most answer them implicitly, through habit and social negotiation and the accumulated weight of precedent. The answers emerge over time, never quite articulated, understood slightly differently by each participant. This works well enough, for a while. Then the project gets big enough, or old enough, or complex enough, and the implicit governance starts to fail.

How implicit governance fails

The failures are quiet. They don't announce themselves as governance failures. They look like creative problems, personality conflicts, or simple confusion.

A contributor holds back from an ambitious idea because they're not sure what's settled and what's open. The world starts to feel frozen, not because anyone decided it should be, but because the cost of getting it wrong is unclear. Caution becomes the default.

Or the opposite: nothing feels settled. A detail established months ago gets casually contradicted, and the contributor who established it discovers their work has been quietly overwritten. Investment in the shared world drops, because why invest in something that might not hold?

The reference document, if one exists, falls behind. Nobody is sure whether it reflects the current state of the world or last quarter's state. Contributors start keeping their own notes, which diverge. The shared world becomes a collection of private worlds that happen to share a name.

A disagreement about the world turns into a disagreement about authority. Someone wants to change something that someone else considers settled. There's no defined process for resolving this, so it becomes a test of social capital: who can persuade more people, who has more history with the project, who is willing to push harder. The governance question gets answered, but through politics rather than process.

None of this requires malice. It's entropy. Shared worlds degrade through the accumulation of small ambiguities, not through dramatic breakdowns. The solution isn't to restrict creativity. It's to make the rules of play explicit.

Rules that enable play

The analogy I keep returning to is game rules, not legal rules.

Legal systems carry adversarial connotations: enforcement, prosecution, punishment. That's the wrong frame for creative collaboration. But game rules do something different. They exist so that play can happen. They're agreed to by the players before play begins. They can be modified by agreement. They don't require external enforcement because participation is voluntary. The rules are what make the game a game rather than a formless activity.

Basketball has rules not because players might cheat, but because everyone needs to be playing the same game for the play to be meaningful. A shot from beyond the arc means something because the three-point line exists. The constraint creates the possibility.

A shared fictional world works the same way. When everyone knows what's settled, what's open, and how changes propagate, creative work becomes more confident, not less. You don't have to check every detail against every other detail before committing a sentence. You know which parts of the world are load-bearing and which are still in flux. You know the process for proposing a change to something established. You can move fast because the structure holds you.

The constitutional analogy is useful here, and it's structural rather than metaphorical. A constitution doesn't list rules; it establishes the process by which rules get made, changed, and interpreted. It operates at a level above ordinary decisions. It says: here are the foundational commitments. Here's how things become settled. Here's how settled things get revisited. Here's what it costs to change something at each level.

A story-world constitution does the same thing. It doesn't replace the bible but sits alongside it. The bible records what's true in the world. The constitution records how things become true, how they change, and who decides.

What a constitution contains

This isn't the place for a full specification; that's what the framework document is for. But the shape is worth sketching.

A story-world constitution defines a canon hierarchy: levels of authority that creative content can hold. Not everything in the shared world carries the same weight. Some commitments are foundational. They define what kind of world this is, and changing them would mean building a different world. Some decisions are established: they emerged from creative work and have been built upon, so changing them means managing a cascade of dependencies. Some content is working, in active use and treated as real but not yet load-bearing. Some is exploratory, explicitly provisional, a space for trying things out without the pressure of commitment.

The hierarchy isn't a bureaucratic ranking. It's a set of practical questions. Before changing something, ask: if this changed, what else would break? The answer tells you what level you're operating at and what kind of care the change requires.

A constitution defines governance roles: not necessarily multiple people, but functions that need to exist. Someone holds the vision. Someone maintains the record. Someone creates. Someone resolves conflicts. In a solo project, one person fills all four roles. The value of naming them is clarity about what you're doing when: the person maintaining the reference document is doing different work than the person writing the next story, even when it's the same person.

A constitution defines a change process for how content moves between levels of the hierarchy. New creative work enters the shared world. Over time, it either hardens (other work builds on it, and it becomes load-bearing) or stays fluid (it can be revised without much cost). Occasionally, something established needs to be reopened. The process for each of these movements is defined, with thresholds that increase as the stakes increase. Changing something foundational should be harder than changing something working, because the cost of the change is higher.

And a constitution is self-amending. The governance itself can be revised, through its own process. If the rules aren't serving the project, the rules can change. This is what makes it governance by consent rather than governance by imposition.

The work of making it explicit

I've been developing this framework in the course of building a shared science fiction universe called Transmission Zero, which currently houses two creative projects set in different eras. The framework, the implementation guide, and the project's own constitution were all written in collaboration with AI, though the approach itself is tool-agnostic. It works just as well with index cards and conversation.

The surprise was how much the act of articulating governance revealed. Implicit rules that had been guiding creative decisions for months turned out to be subtly inconsistent with each other. Assumptions I didn't know I was making became visible when I had to write them down as commitments at a specific canonical level. The constitution didn't just document the governance; it improved it, the way writing always improves thinking.

The deeper surprise was how freeing it felt. With the governance explicit, creative sessions became faster and more confident. I knew what was settled. I knew what was open. I knew the process for changing something that felt wrong. The constitution didn't add overhead. It removed the ambient anxiety of not knowing where the edges were.

That's the thing about good rules. They don't restrict the game. They let you play.