I Built a Worldbuilding Platform Because My Novels Outgrew My Brain
I have a problem that most authors would love to have and few authors knows how to solve.
I’ve written thirty-plus books. Fiction, memoir, philosophy, short stories, a crypto tell-all, an anarchist manifesto built by three AIs, a fairy tale about monkeys and duodenums. Over twenty-five years, these books accumulated characters, locations, factions, artifacts, timelines, and mythologies that started crossing into each other. I did this on purpose — I always knew that I would write a lot and I wanted everything to be connected. Even at first. A character from one novel would show up in another. A technology invented in my satirical Silicon Valley romance would evolve into a decentralized priesthood in a space opera set on Uranus. A hidden sultanate founded by a historical figure in one book would turn out to be the ancestral homeland of a teenager in a completely different series set in Japan.
At some point I looked up and realized I had built something I couldn’t hold in my head anymore.
The Sultanate of Baboob alone has 231 cataloged entries — characters, locations, factions, events, artifacts. Blue Eyed Bastards has 115. Sly Doubt of Uranus has 139. The Fucking People has 92. And they’re all connected. The Waspnest protocol from Petshitter becomes the foundation of the Ethereum Priesthood in Sly Doubt. Aisha Montaigne from my Tama No Michi series is the heir to the Sultanate of Baboob. The Hashishan archive from Hasan i-Sabah shows up in Mehmet’s notebook in The Fucking People. Bald Jesus founds the Ethereum Priesthood. The Walker lineage from Blue Eyed Bastards traces through a turtle-shell box into the Ring origin event.
I needed a system. Not a notebook. Not a wiki. A system that could hold structured data — characters with attributes, locations with geography, factions with loyalties, artifacts with histories — and let me see the connections between them across separate fictional worlds.
That’s why I built W3WU.
What W3WU Actually Is
W3 Worlds Unlimited is a collaborative worldbuilding platform. You create a world, populate it with structured entries — characters, locations, factions, events, artifacts, concepts, magic systems — and set rules for how other people can participate. Open, curated, or paid. You decide what’s canon and what’s lore. You decide who can fork your world and under what conditions.
Think of it like open-source software, but for fiction. Git gave programmers a way to collaborate on code with version control, branching, and merge governance. W3WU does the same thing for fictional worlds. The world creator is the maintainer. Contributors submit entries. Canon is like merging to main — the maintainer decides what’s real. Lore is like a feature branch — it exists, it’s useful, it hasn’t been blessed yet. Forks let someone take a world in a different direction without breaking the original.
The philosophy underneath it comes from something I believe about fiction: worlds are living substrates, not finished products. A world isn’t done when the author says it’s done. It’s done when nobody wants to live in it anymore. And the act of using a world — writing in it, building on it, extending it — is itself a form of authorship.
This isn’t theoretical. I built it because I needed it.
How I Actually Use It
Here’s the concrete reality of what W3WU does for me right now.
It’s my cross-universe continuity database. I have eight interconnected fictional worlds loaded into W3WU: Blue Eyed Bastards, The Fucking People, The Worlds of Sly Doubt, Illuminati Stories, the Anarchists, the Sultanate of Baboob, the Verse Layer, and Future World 2323. Between them, that’s 780 structured entries. When I’m writing or directing a scene in Blue Eyed Bastards Book 3 and I need to know whether the Conver family’s connection to Hasan i-Sabah’s archive has already been established, I don’t re-read three novels. I check the entry.
It’s the backbone of my AI-assisted writing workflow. Currently, I’ve been using Claude Code to read my manuscripts — every line — and extract characters, locations, factions, events, and artifacts into structured entries. Then I push those entries to W3WU via its API. In April, I ran a single batch that processed 361 entities across four manuscripts: BEB2, BEB3, The Fucking People 2, and Sly Doubt Book 2. 237 new entries, 124 updates to existing ones. Zero errors after retry. The API handled all of it.
This is what people don’t understand about how I’m using AI to write new fiction. The AI doesn’t ‘create’ my books, it only writes them. I’ve written thirty-plus books by hand. What the AI does is read them — all of them, cover to cover — and build the reference layer that I can’t keep in my head anymore. Then it populates a structured database that I own, on a platform I built, with an API I control.
It let me build a crossover map. Once the data was in W3WU, I could see connections I’d been making unconsciously for years. I built a visual crossover map — a force-directed graph showing every character crossover, every thematic link, every same-world-different-era connection across my entire catalog. The Sultanate of Baboob turned out to be a hub node connecting to five other worlds. The Verse Layer — a meta-substrate I’d been threading through my books without fully realizing it — emerged as its own hub, connecting Blue Eyed Bastards, the Sultanate, and Hasan i-Sabah through shared mathematics: Cole Briggs topology, the marble constant, seisho notation.
I didn’t know that until I could see it. W3WU made it visible.
It’s how I manage the Anarchist Manifesto Project crossover. The Anarchist Manifesto Project created 26 fictional anarchist personas — each with a unique voice, worldview, and manifesto. Three different AIs built them. When I wrote Blue Eyed Bastards Book 2, three of those personas — Bob Quebec, Emma India, Rudolf Charlie — walked directly into the BEB universe as active characters. Their W3WU entries in the Anarchists world are the source of truth for who they are. When I wrote them into BEB2, I pulled from those entries. The Underground, the Waspnest — those crossed over too. W3WU is the connective tissue that makes that kind of cross-universe writing possible without losing track.
What It Can Do for Other People
Everything I just described — the structured world entries, the canon governance, the collaboration modes — is available to anyone who creates an account.
You create a world. You set it to open, curated, or paid. You populate it with entries — or you invite others to populate it with you. You decide what’s canon and what’s lore. You set fork policies. You set inactivity rules.
For a tabletop game master running a campaign with six players, this means a shared lore bible where the GM controls canon but players can add their own lore entries — character backstories, location descriptions, faction notes — without stepping on each other.
For a writing group building a shared universe, this means structured collaboration with clear governance. Not a Google Doc that anyone can edit. Not a Discord channel where everything scrolls away. A persistent, structured, searchable world with rules about who can say what’s real.
For an author like me with a sprawling catalog, this means sanity.
What It Will Be Able to Do
Here’s where I’m headed.
AI-powered world extraction. Right now, the pipeline that reads my manuscripts and builds W3WU entries runs through my own Claude Code sessions. I’m the only one currently with access to the API but I have build that into the platform itself as a paid layer. Upload a manuscript or paste a chapter. The system reads it, identifies characters, locations, factions, events, and artifacts, and proposes structured entries. You review, edit, approve. Your world populates itself from your own writing.
Cross-world search and discovery. Right now, each world is a silo. I can see connections across my own worlds because I built them and I know where to look. I want to make that automatic. If two worlds both have an entry named “The Waspnest” or reference “the Ethereum Priesthood,” the system should surface that connection. Authors working in the same genre or mythology should be able to discover each other’s worlds — and, if both parties agree, link them. Or if world’s are open, build from them and have that logged.
Reader-facing world exploration. A reader finishes one of my (or anyone’s) novels and wants to go deeper. They open the world on W3WU and browse every character, every location, every artifact. They see which other worlds connect to this one. They follow a thread from the Sultanate of Baboob into Hasan i-Sabah, from Hasan into Blue Eyed Bastards, from Blue Eyed Bastards into Sly Doubt. The world becomes a discovery engine for the books.
Paid worlds and contributor royalties. The platform already supports paid access modes. A world creator can charge for access to their world — and that contributors to that world share in the revenue. Community-driven publishing where the worldbuilding layer has its own economy.
Why This Matters
I’ve been building fictional worlds for my whole life. From D&D to comics to novels. Until recently, they lived only in my notebooks, my books — and in my head. The problem with heads is they forget. The problem with books is they’re linear. A novel gives you one path through a world. The world itself has a thousand paths.
W3WU is the infrastructure for those thousand paths. It’s where the worlds live between the books. It’s where the connections become visible. It’s where collaboration becomes possible without chaos. It’s where a book actually becomes more than a book. Eventually, this is where books will evolve into metaverse worlds. I’m sure of it.
I built it because I needed it. I’m sharing it because every author or creator across all mediums with more than three locations and a recurring character has the same problem. They just don’t know there’s a tool for it yet.
The worlds are living. The platform is live. Come build.
~CD