bedvibe.studio

BedVibe Studios — Engineering

I Use AI to Write My Books. I Wrote the First One by Hand.

Six years, six books, one fantasy world, and a stack of tooling built to stop the machine from drifting. What "AI-assisted" actually looks like when a human directs the whole thing.


A debut novelist recently lost a major book deal after his agents said they could no longer authenticate how the manuscript had been written. I have no idea what that author did or didn't do, and I'm not going to pretend I do. But the argument that followed is one I sit directly inside, so I'd rather say where I stand than let the category swallow me quietly.

I'm the creator of The Mirelands, a dark-fantasy saga I've been building for roughly six years. There are six books in this world.

And yes: I use AI. I use Claude. I use ChatGPT. I use AI throughout the process.

So let me ask the question I think we actually need to ask.

Does that mean I didn't write the books?

If the answer is yes, then I have a second question: could someone else open Claude, type a few prompts, and produce The Mirelands without me?

Because if the answer to that is supposed to be yes, I would genuinely like to watch it happen.

I wrote the first one by hand

This is the part that gets flattened when the whole thing is reduced to "AI-written." The first book was handwritten. No model, no prompt, no pipeline. Just the world and me.

The machinery came later, and it came because I needed it — not because it saved me from writing.

What I actually do: I tell the story out loud

Here is the honest description of my process, and it's stranger than either side of this argument tends to assume.

I am a storyteller before I am a typist. The story arrives as something I speak — scenes, voices, the shape of a chapter, the way a character would actually say a thing. What AI does, once the machinery around it is stable enough to trust, is take what I have spoken as a storyteller and put it into written text. It fixes my grammar. It helps me find a sentence I can hear but can't land. It helps me restructure something that isn't working.

It does not supply the fantasy. It does not supply the ideas. It transcribes and refines a story that already exists, told by a person who has been carrying it around for years.

Sometimes it generates material I reject completely. Sometimes it produces something useful that I then rewrite. I'm not hiding any of that.

But using a tool does not automatically transfer authorship to the tool.

If an editor fixes my grammar, did the editor write my novel? If a voice actress performs my character, did she write it? If a composer scores my adaptation, did he write it? If a game engine renders my world, did the engine create it?

And if an AI helps me generate, revise, transform, verify, or polish parts of the work — at what point does "AI-assisted" suddenly become "AI-authored"?

The world came first, and the world is the hard part

The Mirelands has its own cosmology, history, peoples, kingdoms, characters, creatures, magic, politics, mythology, ecology, chronology, and interconnected storylines.

It has three moons and two skies.

The Silver Moon follows its regular cycle. The Green Moon appears twice a month and changes the experience of the world through the interaction of moonlight, plants, insects, and the environment. The Red Moon appears only twice a year, stays for ten days, and brings a completely different biological and psychological horror with it — it changes the behaviour of people and awakens enormous creatures from the swamps.

Those aren't prompts I threw at a model and then discovered. Those are pieces of a world I have been designing, connecting, and revising for years.

And the books aren't six unrelated outputs. They sit on the same timeline, seen from different perspectives, with different peoples and factions experiencing the same events from different angles. The lore has to stay consistent across the entire saga.

Why I had to build machinery: characters drift

This is the failure mode nobody outside the work talks about, and it is the reason my process looks the way it does.

If you write with an AI, voices drift. Left alone, every character slowly converges on the same register — the model's own. Brakka starts talking like Synovia. Synovia starts talking like Mirae. The distinctions you spent years building erode one paragraph at a time, and they erode smoothly, so you don't notice until a whole chapter sounds wrong.

So each character had to be built as a personality that could be held to. And to hold anything to anything across hundreds of thousands of words of interconnected material, I had to build a RAG-based canon and verification system — something that checks the books against the world I created and tells me when the world has slipped.

That system is not a convenience. It is the thing standing between a six-year saga and mush.

The other six years

When people hear "six years," they picture six years of typing. That isn't what happened.

I travelled. I spent around €30,000 on studios, studio equipment, and voice actresses and actors, recording real human performance. I curated audio datasets — and wrote Rust binaries to do it, because the tooling I needed didn't exist. I trained custom text-to-speech models and built wrappers around them for normalisation and QA. Two of those QA layers became open-source tools in their own right: ttsproof and trainproof.

Then I took the books beyond the books: web games set in the world, additional lore, ebooks and paperbacks, audiobooks, and full dramatized audio adaptations. For the audio productions I went through the books practically scene by scene, turning narrative prose into dialogue and performance — because a novel and an audio drama are not the same object. Narration has to become action, timing, atmosphere, and a voice in a room.

AI is involved in those processes too. So what exactly are we calling that?

"AI-written" is hiding everything that matters

There's an enormous difference between:

"I asked a model to write me a fantasy novel and published the result."

and

"I spent six years building a fictional universe, wrote its books, designed its continuity, developed its characters and mythology, directed its adaptations, built games and lore around it, and used AI as a set of tools throughout the creative and production process."

Those are not the same thing, and one bucket cannot hold both.

Some people use AI to avoid writing. Some use it to write. Some use it as an editor. Some as a brainstorming partner. Some as a production tool. Some build entire creative pipelines around it. Those aren't interchangeable, and "human-written" versus "AI-written" conceals every difference that actually matters.

Where I draw the line

Writers should be honest about what they use AI for. That's the part I think is genuinely non-negotiable, and it's why this article exists.

But the conversation also has to be honest about what the human actually did.

If I use AI in my process, does that make six years of work worthless? Did the worldbuilding disappear? Did the characters? Did the six years?

I didn't wake up one morning and find The Mirelands sitting inside Claude. I built it. The AI became part of the machinery I used to bring it into existence.

And that's the uncomfortable question underneath all of this: when AI becomes part of an artist's toolkit, are we going to judge the existence of the tool — or are we going to look at the human being who conceived, directed, revised, rejected, connected, built, and ultimately decided what the work became?

I'm genuinely curious where people draw that line. I'm not offering any of this as proof that AI had no role. Quite the opposite. It's an invitation to look at what an AI-assisted creative project actually looks like when a human has spent years directing the whole thing.

The work itself