Constitutional Worldbuilding: The Reference Documents
Over the past several weeks, this series has been developing an idea: that shared fictional worlds need explicit governance, and that the right kind of governance enables creativity rather than constraining it. We've talked about why governance matters, how canonical levels work, why stewardship is critical, how multi-project worlds flow, and why consent is the load-bearing principle.
Those posts are essays. They explore the ideas, argue for them, connect them to other things. They're meant to be read in order, and they build on each other. But behind the essays sit two documents that do something different: they specify. Not "here's why this matters" but "here's how it works."
Today those two documents are published as standalone reference pages on this site.
The Governance Framework
The Collaborative Fiction Governance Framework is the complete specification. Five components: a canon hierarchy that distinguishes foundational commitments from working decisions, an authority structure that names the roles every shared world needs, a change process that defines how content moves between levels, a consistency protocol for detecting and resolving contradictions, and a meta-governance layer that makes the framework self-amending.
The framework is tool-agnostic and scale-independent. It applies to a solo author managing consistency across a long series, a writer's room maintaining a shared universe, a tabletop RPG campaign tracking accumulated lore, or an open fan community governing a collaborative world. The structural components are the same; the parametric settings change.
The Implementation Guide
Implementing a Story World Constitution is the practical companion. Where the framework says "you need canonical levels," the implementation guide says "here's how to choose how many, here's how to designate your existing content, here's what the steward actually does on a Tuesday." It walks through the five steps of setting up governance, identifies common failure modes, discusses how governance complexity scales, and develops the tree model for multi-project worlds.
The implementation guide is where the framework meets the ground. It's the document you'd actually open when sitting down with collaborators to establish governance for a specific project.
Why these aren't posts
The posts in this series are arguments. They have a point of view, a rhetorical structure, a beginning and an end. You read them once, maybe revisit them if the ideas are useful.
The framework and implementation guide are reference documents. You don't read them front-to-back and put them away. You consult them when you need to set up governance, when you need to resolve a canonical conflict, when you need to check whether your project's stewardship is healthy. They're designed to be returned to.
That's a different kind of writing, and it belongs in a different place on the site. The posts live in the chronological flow. The documents live in their collection, alongside the posts but separate from them, available to be found and used on their own terms.
What's next
The constitutional worldbuilding series has laid out a complete system: theory in the posts, specification in the framework, practice in the implementation guide. The system is being applied to a real project (the Transmission Zero shared universe), and the experience of applying it will generate new observations worth writing about.
But the next time this series appears, the foundation will be something you can point to and read. That was the goal.
This work is marked with CC0 1.0 Universal. To the extent possible under law, the author has waived all copyright and related or neighboring rights to this work.