Systemic worldbuilding for games, anime, manga, and transmedia IP. Structure, consequence, and architecture — from premise to handoff.
Every project is a proof of concept in interactive narrative and mechanical consequence. The worlds we make are not backdrops — they are the mechanic.
Builds worlds with internal logic — and stories that test what happens when that logic breaks. Practice sits at the intersection of structure and consequence: every magic system, political hierarchy, and cultural myth exists because it must, not because it's decorative.
Approaches worldbuilding with the same rigor an architect brings to load-bearing walls. All concepts, worldbuilding, and narrative systems are human-originated — AI used only for formatting and grammar, never for ideation or core content generation.
An underground civilization has spent generations fearing the surface world — until a surface archaeologist uncovers a devastating truth: their founding myth was engineered, and the royal family are the architects of a millennia-long conspiracy against their own people. A covert cold war of information, control, and resource extraction played out through Heartstones — semi-sentient crystalline organisms governed by emotional resonance.
Every engagement starts here. We define the central premise — what this story is fundamentally about — and establish the core rule set that everything else must obey. This isn't about tone or aesthetic. It's about identifying the load-bearing idea: the emotional, mechanical, or philosophical logic that makes this world distinct. If the core is vague, the world will be vague. If it's precise, the world will hold.
With the core locked, we build outward. Factions, locations, histories, characters, magic systems, political structures — all developed in relationship to the core, not independently of it. Each element is stress-tested against the world's internal logic before it's documented. Nothing gets added because it's interesting in isolation. Review cycles happen throughout, not just at the end.
The completed system is delivered as a fully organized, cross-referenced design document in a format your team can immediately work from. Every entry is indexed. Every decision has a rationale. Dependencies between elements are mapped so that when something changes, you know exactly what else is affected. A handoff session walks through the full architecture so your team can maintain and expand the world without needing me in the room for every call.
Eight questions covering services, process, timelines, pricing, and scope.
If you're building something with real narrative stakes and want a collaborator who takes story architecture seriously — let's talk.