Behind the Forge

Before the first chapter review

The World Before the Collaboration

Andellian had been with me for roughly fifteen years before I asked ChatGPT to examine a single chapter.

It began as most private worlds probably do: with fragments. A blacksmith. A road. Two people who wanted a quiet life. Gods with old grievances. Cities, histories, religions, monsters, and stories that existed long before I knew which of them belonged in a novel.

Over time, those fragments became a world. The world became a plot. The plot became an approximately 114,000-word manuscript.

That manuscript was mine in every way that mattered. The characters, their relationships, the history behind them, the shape of the series, and the ending I intended had already been carried for years. I had not asked a machine to imagine Andellian for me. I had finally written down enough of Andellian to discover how difficult it was to judge from the inside.

There is a particular blindness that comes from knowing a world too well. I knew why every road had been built, which god had broken which promise, and what a seemingly minor object would mean four books later. The reader did not.

The first manuscript contained the story I wanted to tell, but it also contained years of accumulated explanation, repeated emotions, buried revelations, and pieces of lore I loved more than the chapter carrying them could afford.

The choice was not whether to preserve the world. The choice was whether I was willing to rebuild the book.I was.

The project had to survive the chat

The Day the Conversation Ended

The first time a conversation reached its limit, I panicked.

For months, the work had lived inside one long exchange: chapter notes, revisions, decisions about characters and magic, and the private logic of a world I had carried for fifteen years. Then the conversation stopped. I could not continue typing into it. For a few terrible minutes, it felt less like a software limit and more like the door to the workshop had closed with the manuscript still inside.

I moved into ChatGPT Work, tried to reconstruct the project, and began rebuilding the context piece by piece—what had been approved, which files controlled, what could not be revealed yet, and how the voice was supposed to sound. Only later did I discover that I could return to a normal conversation and continue. The project had not vanished. The collaboration had not vanished. But the fear had done useful damage.

The conversation was not the project.

A manuscript this large could not depend upon one chat, one remembered summary, or one file with an impressive name. We began building canon bibles, revision ledgers, source hierarchies, versioned masters, handoff prompts, and recovery packages. Every new conversation had to know which manuscript controlled, which decisions were locked, and which mysteries were still meant to remain mysteries.

Those systems did not appear because we were brilliantly organized from the beginning. They appeared because I got scared.

And that fear changed the way we worked. The collaboration became more durable, more disciplined, and more honest about its own limits. I learned to ask not only whether a revision was good, but whether it had actually been saved in the right file. ChatGPT learned—sometimes after being corrected—that a remembered decision was not the same thing as verified text.

The moment was frustrating, embarrassing, and eventually funny. It was also the day the project stopped living inside a conversation and became something built to survive beyond one.

Argument was part of the method

Real Disagreements

The collaboration worked because agreement was never the goal. The goal was to make the book better.

Some discussions ended with my accepting ChatGPT's recommendation. Others ended with me rejecting it. A few ended with both of us discovering that the first question had been wrong.

Bellweather or Tarken?

One of the cleanest examples came when choosing the first free story offered to readers. ChatGPT preferred The Troll of Tarkenas the stronger introduction to Andellian's broader fantasy identity. I preferred The Eighth Morning of Bellweather because it felt more distinctive, more surprising, and more likely to show readers the range of the world before asking them to enter the novel.

We argued the merits. Bellweather became the free signup tale. Tarken did not disappear. It moved into the later reader sequence, where it could do a different job.

The Page That Contained “Nothing.”

During paperback production, one page appeared almost empty except for a single word: Nothing.

At first, ChatGPT praised it as an elegant accidental pause. I disagreed. The line worked when it appeared naturally at the end of the preceding scene. Forced onto an otherwise blank page, the typesetting became visible.

Removing the page would have changed the final page count and required adjustments to the cover. Rather than preserve a weak effect or rebuild the entire package, we used the space for a regional map of the places traveled in Book One. The final solution was better than either starting position.

When the Continuity Editor Was Wrong

During one review, ChatGPT flagged several apparent problems: a missing hammer recovery, an incorrect delay, a character's religious status, and what looked like a misspelled name.

I knew the answers. The recovery had already been established. The event had happened immediately. The character had made his religious choice. The odd name was deliberate personal speech.

A tool can identify a question. It cannot decide what the story means.

Files become an object

From Manuscript to Physical Book

Revision ended only when production began.

Once the prose was locked, the work changed shape. Chapters became master files. Master files became print interiors. Margins, page turns, headers, maps, image placement, metadata, and proof copies became part of the story.

In KDP's digital Previewer, I noticed that the text on some pages seemed too close to the inside margin. ChatGPT reviewed the screenshots, saw that the text remained inside KDP's safety lines, and concluded that the mirrored margins were acceptable.

The physical proof proved otherwise.

The odd-numbered pages sat too close to the spine. The interior went back into production, the margins were corrected, and a second proof was ordered.

Another problem appeared around a nearly empty page containing only one word: Nothing. Moving the line would have altered the page count and affected the cover, so the empty space became something better: a black-and-white regional map showing the roads, settlements, mountains, and rivers traveled in Book One.

This time, the odd pages sat correctly. The map printed cleanly. The text opened comfortably away from the gutter.

It's perfect.

That moment mattered because the book was no longer an idea, a manuscript, or a file awaiting one more correction. It was a physical object I could place in my hands.

The work continued outward from there: the website, reader mailing list, ebook preparation, launch planning, press materials, and a premium hardcover edition designed to belong among the hundreds of hardcovers already on my library shelves.

The definitive version will be black linen, gold foil on the spine, cream paper, and a matte dust jacket.

Some books are finished when the final sentence is written. This one had to survive the forge.