Why AI books feel wrong

You picked up a book, or downloaded a sample, and a few pages in you stopped. Something was wrong with it. You could not have said what. The sentences were grammatical. The words were spelled right. The story, on paper, had everything a story is supposed to have, a character, a problem, some stakes. And yet you closed it, or you pushed through to the end feeling vaguely cheated, and you came away with the sense that you had been reading something hollow. If that has happened to you more and more lately, you are not imagining it, and this article is about why.

I am going to do two things here. First, name the thing you are feeling as a reader, the specific off-ness of machine-written books, because once you can name it you can stop wondering whether the problem is you. Then, because a lot of the people reading this write their own books and use these tools to do it, I am going to turn it around and explain what you have to fix if you do not want your readers feeling that same off-ness about your work. The reader’s experience and the author’s problem are the same thing seen from two sides. And the fixing is learnable: this is the first step of a method that the series builds toward, a way to draft with AI and still hand your reader something that holds.

The feeling has a name

The feeling is hollowness, and it is real, and it is specific. It is not the same as bad writing. We have all read bad books by human authors, books with clumsy sentences and limp plots and characters made of cardboard, and they feel bad in a familiar way. This is different. A machine-written book can be smoother than the human one, cleaner at the sentence level, more competent on the surface, and still produce a sensation the clumsy human book never does. The clumsy human book feels like someone trying and not quite managing. The machine book feels like no one is there.

That is the thing readers are picking up on, even when they cannot articulate it. Behind a human book, however flawed, there is a person who wanted something, who chose these words because they meant something to them, who left fingerprints. Behind a machine book there is a very sophisticated averaging of everything that has ever been written, arranged into the shape of a book, with no one underneath who needed it to exist. Readers feel the absence of that need. They feel the missing person. The hollowness is the shape of the hole where a writer should have been.

For a long time readers could not catch this. The machine got good fast, and for a while it could pass, and a lot of people read machine prose without knowing it. That is changing, quickly. Readers are developing an ear for the absence, the way you develop an ear for a faked accent, and once developed it does not switch off. More and more people read a few paragraphs and feel the hole, and put the book down, and could not tell you why except that something was off. You are part of that growing group, and the off-ness you feel is a skill, not a fault.

Why it is so hard to put your finger on

Here is the part that makes this maddening as a reader. The hollowness is real, but the moment you go looking for the cause, it hides. You scan back over the page trying to find the bad sentence, and there is no bad sentence. You look for the plot hole, and the plot is intact. You hunt for the thing that broke the spell, and you cannot find it, and so you start to doubt yourself, to wonder whether you are being unfair, whether the problem is your mood or your attention rather than the book.

The reason you cannot find it is that the off-ness is not in any one place. It is distributed. It lives in a hundred small choices across the whole book, no one of which is wrong on its own, which add up to the feeling of no one being home. A single machine sentence looks fine. It is the accumulation, the same handful of moves repeated at every level for three hundred pages, that produces the hollowness, and accumulation is exactly the kind of thing a reader feels but cannot point to, because pointing requires a single location and there isn’t one.

This is why “it just felt off” is the most common reaction to machine books and also the most frustrating, because it sounds like nothing, like a vague complaint, when it is actually an accurate read of a real problem. The problem is structural and pervasive, not local, and a structural pervasive problem registers as a mood rather than a fault. The reader is right. They just cannot show their work, because the evidence is everywhere and nowhere.

The rest of this article, and the series it introduces, is an attempt to give you the words. To take that vague, accurate, frustrating feeling and break it into the specific, nameable patterns that produce it, so that the next time a book feels off you can look at it and say, there, that is the held breath, that is the rule of three, that is the ending that healed everything it should have left broken. Naming it does not make the feeling go away. It makes it legible.

The five places the hollowness comes from

The off-ness has five sources, and they sit at five depths, from the surface of the prose down to the bones of the story. I have written a full article on each, and together they make up a series that walks all the way down. Here is the short version of where the hollowness actually lives.

It lives, first, in the words. The machine reaches for the inflated, slightly abstract version of everything, “delve” for look, “journey” for process, “navigate” for handle, because it does not trust the plain word to carry. This is the layer everyone already half-knows, the famous one with the word lists. It is the shallowest source of the off-ness and the one you are most likely to have already noticed.

It lives, second, in the sentences. Even after the suspect words are gone, the rhythm gives it away, a flat, even cadence built from the same constructions over and over, the not-just-this-but-that reflex, the relentless rule of three, the hedges, the run-ons. The sentences sound composed, balanced, and somehow lifeless, and you feel it as a music that never surprises you.

It lives, third, in the paragraphs. The machine builds nearly every paragraph the same way, announce the point, develop it, restate it, then do it again, in blocks of nearly identical length, so the whole book marches with a mechanical evenness. This is the layer where the prose stops feeling like a person thinking and starts feeling like an outline that got dressed up.

It lives, fourth, in the scenes. This is where the hollowness gets loudest in fiction, because rendering real experience requires having had some, and the machine has not. Characters watch themselves from the outside. Everyone speaks in clean, complete sentences. Emotions get named instead of felt. The same small kit of gestures, the held breath, the tightening chest, recycled endlessly. The scene is described rather than inhabited, and you feel the difference as a pane of glass between you and the moment.

And it lives, fifth and deepest, in the spine, the structure of the whole story. This is the real source, the one under all the others. The machine will not let anything cost what it should cost. It raises stakes and never makes anyone pay them. It heals every wound. It gives every character a clean arc, redeems every antagonist in convenient ways, states its theme and restates it, and resolves everything by the end so that nothing is left broken. This is the deepest reason machine books feel hollow: they are structurally incapable of letting a story hurt, and a story that cannot hurt cannot move you.

And there is a sixth source standing next to the spine: content cowardice, what the machine refuses to put on the page at all. It will not write the genuinely brutal scene, the genuinely explicit one, the genuinely cruel one, unless forced, and even then it flinches and pulls the camera back at the worst moment. It writes to please you rather than to tell you the truth, steering always toward your comfort, so the whole work lives in a safe middle register and never goes to the extremes where the strongest reading experiences live. Where the spine is the machine flinching from consequence, this is the machine flinching from the material itself. It is why machine fiction feels not just hollow but housebroken.

Why the spine is the real culprit

If you want to understand the hollowness in one idea, it is this. A story moves you when it costs something. When the character loses what they cannot get back, when the wound does not heal, when the ending leaves you carrying something you cannot put down, that is when a book stays with you, because the cost made it real. The machine cannot do cost. At the deepest level of its construction, it is built to reassure, to resolve, to make everything okay, and so it systematically removes the one thing that would have made the story matter.

This is why you can finish a machine book that did everything right on the surface and feel nothing. The competent words, the clean sentences, the tidy paragraphs, the smooth scenes, all of it was in service of a story that refused to make you pay, and a story that refuses to make you pay gives you nothing to feel. The hollowness you felt was the absence of cost. The book promised stakes and then quietly cancelled them, healed what it broke, and sent you off with a smile, and you walked away empty because there was nothing to carry.

The four shallower layers are real, and they contribute, and a reader catches them. But the spine is why the whole thing falls flat even when the surface is clean. You can scrub every word and fix every sentence and the book will still feel hollow if its bones are built to avoid all cost. That is the thing under the thing, and it is the reason this series exists, to get past the words, which everyone fixates on, and down to the structure, which is where the off-ness actually comes from.

What the hollowness feels like in practice

Let me get concrete about the experience, because naming the feeling in the abstract only goes so far. You know the off-ness through specific moments, and you have probably had all of these without connecting them.

You finish a chapter and realize you felt nothing, despite the chapter clearly being built to make you feel something. A character died, or confessed, or triumphed, and you registered the event the way you register a plot summary, from the outside, untouched. The machine rendered the beat correctly and you stayed completely dry-eyed, and you wondered briefly whether something was wrong with you, whether you had become too jaded to be moved. Nothing is wrong with you. The beat was hollow. It went through the motions of an emotional moment without the cost that would have made it land.

Or you find that you cannot remember the characters an hour after you stop reading. They had names, and roles, and even backstories, and yet they leave no residue, because they all thought and spoke and reacted in the same smooth average voice, and a cast of variations on one voice does not populate a memory. The human books you love left people in your head who feel like people you knew. The machine book leaves a pleasant blur.

Or, most tellingly, you reach the end and feel a small click of dissatisfaction precisely because everything worked out. The threat was defeated, the wound was healed, the lovers united, the lesson learned, and instead of satisfaction you felt a faint emptiness, a sense of having been handed something too easy to be worth having. That click is you registering the spine. The story refused to make anyone pay, and on some level you knew it, and the tidy ending read as a cheat rather than a reward. The books that stay with you are usually the ones that did not give you that clean resolution, that left something open or broken or unbearable, and the machine cannot do those, which is exactly why its endings ring false.

Once you start noticing these specific experiences, you will find they cluster around machine writing with uncanny reliability. The dry eye at the emotional beat. The characters who evaporate. The ending that satisfies on paper and disappoints in the gut. These are not random reactions. They are you, correctly, feeling the absence of cost at the places where cost should have been.

Now the other side: why your own AI books keep failing

A lot of you reading this are not just readers. You write, and you use these tools to do it, and you have published or are about to publish a book that had machine help, and some part of you is worried it has the off-ness too. Good. That worry is worth listening to. Let me turn the whole thing around and tell you, plainly, why your AI-assisted books are not landing the way you hoped, and what it would actually take to fix that.

The first hard truth is that the thing you probably did to fix it did almost nothing. You ran down the word list. You swapped “delve” for “look at,” cut the em dashes, replaced “leverage” with “use,” and you felt the satisfaction of watching the obvious tells disappear, and you believed the book was clean. It was not. You fixed the shallowest layer, the one readers were least bothered by, and left the four deeper layers completely intact. The hollowness your readers feel is not coming from the words you fixed. It is coming from everything underneath that you did not touch.

The second hard truth is that the layer you most need to fix is the one you cannot fix by editing. The spine, the structure, the willingness to let the story cost something, is set before the prose exists. By the time you have a machine draft in front of you, the cowardice is already baked in, the stakes already toothless, the ending already healing everything, the arc already clean. You can polish that draft forever and it will still feel hollow, because the hollowness is in the skeleton, and you cannot sand a skeleton into a different shape. You have to rebuild it, which means deciding, before you generate a word, what your story is going to take from its characters and not give back, and then holding that decision against the machine’s relentless pull toward comfort.

The third hard truth is the one nobody wants to hear. Doing this well is not faster than writing the book yourself. The fantasy of AI authorship is that you generate a draft and lightly clean it and you have a book in a weekend. The reality, if you care whether the book lands, is that cleaning a machine draft down all five layers, especially rebuilding the spine, is real work, often more work than drafting from scratch would have been, because now you are fighting the machine’s choices at every level instead of making your own. The tool is genuinely useful for drafting, for getting unstuck, for grinding through a passage. It is not a shortcut to a book that moves people. There is no shortcut to that. There never was.

A word for the reader who feels guilty about it

Some readers, having noticed the off-ness, feel bad about it. They worry they are being unfair, that they are prejudging a book because they suspect a machine was involved, that they have become snobs who cannot enjoy anything anymore. If that is you, set the guilt down. You are not being unfair, and here is why.

You are not reacting to a label. You did not check the book’s production method and then decide to dislike it. You felt the hollowness first, in the actual reading, before you knew or suspected anything about how it was made. The off-ness came to you unbidden, through the prose itself, which means it is a response to the writing and not a prejudice about its origin. A genuine prejudice would make you dislike a book because you heard it was AI-assisted. What you have is the reverse: you feel the writing fall flat, and only afterward, if at all, do you wonder about the cause. That is discernment, not bias.

And your discernment is doing something valuable, for you and for writing in general. Readers who can feel the absence of cost, who put down the hollow book and reach for one that risks something, are the immune system of literature. They are the reason the machine cannot simply flood the world with frictionless, costless, comfortable prose and have it accepted as the real thing. Every reader who feels the off-ness and trusts that feeling is a small vote for writing that actually does the hard thing. You are not a snob. You are part of what keeps the bar where it belongs.

So trust the feeling. When a book feels hollow, it probably is, and the fact that you cannot immediately point to why does not make you wrong. It makes you early. The why is what this series provides, and once you have it, the feeling you have been half-apologizing for turns into something you can state with confidence.

What fixing it actually requires

Before the order of operations, the thing nobody warns you about: fixing a machine book feels like whack-a-mole, and there is a reason it feels that way. Every fix reveals the next problem. You clean the obvious words and notice the sentences are all the same length. You vary the sentences and notice every paragraph has the same shape. You fix the paragraphs and notice the characters keep watching themselves, then that the dialogue is too clean, then that the eyes changed color in chapter eight, then that the voice drifted halfway through and the back half does not sound like the front. You are never done, because the layers go all the way down, and the moles keep coming faster than you can swing.

That experience is real and it is worth naming, because it breaks people. They start out believing they are doing a quick cleanup, and the cleanup never ends, and they cannot understand why, and they conclude they are bad at editing. They are not bad at editing. They are playing an unwinnable game. The shallow moles can be whacked, with enough passes, but underneath them is the one mole that is not a mole at all: the spine, the machine’s single unchanging structure, the chapters all the same length, the stakes that pay nothing, the tameness, the sameness. You cannot whack that. It is not a defect in the draft. It is the draft. And the only move that works is to stop whacking and rebuild from the structure out, which is not editing, it is writing the book, the thing the machine was supposed to spare you.

There is also a phenomenon that only appears at length, and it is part of why the back half of a machine book is always worse than the front. Over a long generation the machine drifts. The facts stop matching, eyes change color, names shift, a plot thread set up early just evaporates because the machine no longer holds the fact that it set it up. And the writing itself degrades, the specific voice you asked for eroding back toward the machine’s defaults the further it runs, so the tenth chapter is blander than the first. This drift is invisible in a short sample, which is exactly why people test the machine on a paragraph, see something clean, and trust it with a book it cannot hold. The drift article covers this in full.

The honest order of operations

If you want your book to land, here is the honest order of operations, and notice that it runs opposite to how most people work. Most people start at the words, because the words are visible and the fix is satisfying, and they stop there. You should start at the spine, because the spine is the source, and work upward.

Start by deciding what your story costs. Name the thing that will be gone at the end that was not gone at the start, and make it something that matters, and commit to it before you generate anything, because the machine will not invent a real cost and will quietly remove any cost you do not defend. Decide which characters genuinely change and let the others stay the same. Give your antagonist a real case, an argument you cannot easily dismiss. Choose your structure and hold it against the machine’s pull toward the tidy three-act shape. This is the spine work, and it is the work that matters most and the work almost no one does.

Then, with the bones right, work upward through the scenes, getting your characters back inside their own bodies, roughing up the too-clean dialogue, cutting the emotions you named and trusting the actions to carry them. Then the paragraphs, breaking the even blocks, cutting the announced points and the restatements, letting the rhythm vary. Then the sentences, hunting the rule of three and the hedges and the flat even cadence. And last, the words, the layer you probably started with, which turns out to be the final polish rather than the main job.

Work in that order and you will produce something that does not feel hollow, because you will have put back the one thing the machine removed, which is the cost, and you will have put yourself back into the book, your choices, your willingness to let it hurt, the fingerprints that tell a reader someone is home. That is the whole job. It is not swapping words. It is refusing, at every level, the machine’s instinct to make everything smooth and safe and resolved, and insisting instead on the specific, the costly, and the true.

Where to go from here

If you are a reader, you now have the beginning of a vocabulary for the thing you have been feeling. The next time a book feels off, you will have somewhere to look, and the five articles in the series will give you the rest of the words, layer by layer.

If you are a writer, you now know why your cleanup has not been working and what it would actually take. The series lays out each layer in full, with the specific patterns to hunt and the specific fixes to make, and a pair of full stories, one machine-written and one rebuilt, so you can see the whole thing done.

Either way, start with the series hub, which lays out the full descent through all five layers, and then read down from the surface to the spine. The off-ness you have been feeling is real, it has five sources, and by the end you will be able to name every one of them.