写了两遍的小说

The Novel I Wrote Twice

> By Li Xiaolai · 2026-07-10 · [Original link](https://lixiaolai.com/articles/2026-07-10/the-novel-i-wrote-twice)

On June 1st — Children's Day, as it happens — I started writing my first novel. On June 20th I published it on GitHub. Most stories about writing with AI end right there, on the impressive number: a novel in twenty days. Mine doesn't end there. On July 10th I published the novel again — same title, same case, same facts — and almost nothing else survived. In between, I demolished my own book on purpose and rebuilt it from the foundation. Thirty-nine days, 869 commits, not a single day off.

People ask how anyone writes a novel in thirty-nine days. I think that is the wrong question. The right question is how anyone can afford to write it twice.

*Too Late* (《迟到》) is a novella in Chinese: seventy-some thousand characters, seventy-five scenes. On New Year's Eve 2003, a man dies on a school construction site in a small county town and is buried under what will later become the playground. On paper, nothing happened that night. His wife keeps a steamed-bun stall by the school gate and mails petition letters, year after year, never once making a scene. Sixteen years later an anti-gang inspection team enters the county, and a woman behind the petition-office window — the one whose job is to stamp *case closed* — is dragged, step by step, back to that night.

Chinese readers recognize the case immediately; it was reported nationwide. The people, their motives, and everything that happens between them are invented. That one sentence — *the case is recognizable, the people are invented* — turned out to be the most load-bearing rule of the whole project. It sounds like a legal disclaimer. It is actually a research discipline, and the rest of this article is mostly about what that discipline cost and what paid for it.

When I wrote about the first version in Chinese, I said that imagination is the kind of beauty that only shows itself dancing in shackles, and that logic is the shackles — every link in the chain forged from research notes. What I could not show then, because I had not counted yet, is how much iron went into the chain.

The main characters of *Too Late* are a county-town policewoman turned petition clerk and a hospital nurse. To write those two people credibly you need to know, at minimum: how a petition window actually processes a letter, and what it means bureaucratically to stamp it *resolved*; how a case file moves between a county police bureau, a city procuratorate, and a provincial court, and at which desk it can quietly stop moving; what a nurse's shift actually consists of, hour by hour; how a county cadre gets promoted, and what he will and will not put in writing on the way; how a national anti-gang inspection campaign descends on one county in 2019, who it frightens, and in what order; what a county town *sounded like* in 2003 — the ringtones, the stove smoke, the school loudspeakers — versus what it sounds like in 2019. None of this yields to "just imagine it." Readers who grew up in such a town hold a lifetime of calibration data, and they will catch you in one wrong sentence.

This is the work AI has changed beyond recognition. The research library for this novel ended up at sixty-three files — in bulk, approaching the length of the finished novel itself — covering the institutions, the timelines, the evidence chains, the era. It includes things I would never have commissioned in the old world because they would have been absurdly expensive: year-by-year "sound and image slices" of one county town across sixteen years; an organizational dossier on every institution the plot touches; a working model of county officialdom built on a celebrated doctoral field study of one county's cadre system. In the old world, this is a year or two of desk research. It took days. I have said the efficiency gain is tenfold; having now counted, I think I was being conservative.

But speed was the smaller half of the change. The larger half was discipline. The fact library had rules: every entry graded by source quality; facts written into it only by me, by hand — the AI's job was to verify and challenge, never to author; and a hard firewall between the fact side and the fiction side, with a mechanical guard making sure no real person's name could leak across. Research this fast is dangerous precisely because it is fast — it will happily hand you plausible sludge at the same speed as truth. The library was built the way you would build it if you expected to be cross-examined. Eventually, I was. I'll get to that.

Here is the number that surprised even me. The published novel is about 73,000 characters. The folder of proposals, outlines, discarded devices, structural memos, and cold-reading reports written along the way holds 927 files — roughly three and a half million characters. Call it fifty characters written and thrown away for every one that shipped.

That ratio is the honest shape of fiction, and it is where AI earned its keep — not by writing the book, but by making the thinking around the book cheap enough to do properly. I kept what amounts to an editorial office that argues back: a panel of advisors who read every structural proposal and attack it — one channels Aristotle on plot unity, one Lajos Egri on premise and character, one Robert McKee on the dramatic engine, one Ursula K. Le Guin on the sentence and the point of view, one a scholar of county politics who flags every place an official acts the way plot convenience wants instead of the way the machine he lives in wants. The standing rule for all of them: pressure-test before building, and no "yes, and" — if you disagree, say so plainly and say why. An advisor who flatters is a dead weight; I have no use for a chorus.

Under all that argument, exactly one AI was ever allowed to hold the pen and produce draft prose, under a style rulebook, one scene at a time. And above it sat an editor-in-chief — me — who worked over every line and made every call that mattered. On the last day before publication I was still changing single words of dialogue by hand: one character got "these days" where the draft said "now," because that man is a marketplace talker who never says anything straight, and *now* was too plain for his mouth. The machine drafts; the machine argues; the machine checks. What a character would never say — that stayed my job.

That division of labor was not a stylistic preference; it was forced on me by something I learned coming to fiction from software. I write software with AI every day — the editor I am typing this sentence into is some hundred and fifty thousand lines of code, and AI agents patrol and repair it around the clock, superbly. Hand the same machines prose, and what comes back is never quite writing. This is not a maturity gap the next model will close; it is the nature of the two materials. Code is a formatted language: it has a compiler, a test suite, a definition of correct that lives outside any reader — and a machine can iterate against that outside verdict until the thing is right. Natural language has no compiler. A sentence answers to nothing but a reader's ear, and every ear was calibrated by a life. Worse for the machine: in code, sounding like no one in particular is a virtue — we call it convention. In prose it is the one unforgivable failure, and the model's great averaged voice — the very thing that makes its code so dependable — is exactly what it cannot shed on the page. So the machine's drafts were useful to me the way lumber is useful. The carpentry could not be delegated.

Before the first version ever shipped, eight structural architectures had already been built and torn down. The version I published on June 20th was the eighth. Remember that number.

I put the novel on GitHub — full text, EPUB, print-ready PDF — and invited readers to file issues: logical holes, professional errors, anything that read wrong. Eight issues came in. Some were typos. One was a sharp question about how a character in scene six could know what he knows. One was a full editorial review — structure, language, plot logic, medical facts, proofreading — of the kind you would pay a publishing house a great deal of money for, if a publishing house still sold it.

The medical one is my favorite, because it shows the whole method in miniature. The novel needs a man who cannot answer a question for sixteen years — alive, present, and silent. The draft said locked-in syndrome and moved on. A reader pushed on the medicine: classic locked-in patients can still answer yes and no with their eyes; your sixteen years of silence has a hole in it. Back to the literature — hours, not weeks, because the research engine was still warm — and it turns out the fix was two sentences: the character has the complete form, named on the page, the rare type that takes even the eyelids. Two sentences, and a sixteen-year premise became medically watertight. That is what AI-assisted research feels like in practice. It is not grand. It is a reader's letter answered properly by dinnertime.

I ran my own audits in the same spirit, and the two worth telling are the ones that could have ended in embarrassment. First, the voice test: I had claimed each major character spoke distinctly, and a claim like that deserves to be falsifiable. So: twelve characters, ordinary mid-grade lines from each — famous lines banned — names masked, and an AI from a different company asked cold: who is speaking? Twelve out of twelve, with reasons. It knew one character because he "converts concern into money the moment he opens his mouth," another because her *case closed* comes out "cold and procedural." Second, the cold read: a rival model family, blind, no context, all seventy-five scenes. It scored the draft seven out of ten and put its finger precisely on a sagging stretch in the middle third. The sag was real. Those scenes got surgery.

Now, the part that makes this a different article from the one I wrote in June.

The reader reports and my own re-reading converged on something no line edit could reach: the first version was built wrong. Its protagonist witnessed; she did not want. Scene after scene was a beautifully researched tableau of suffering with nobody driving. You cannot patch that, any more than you can renovate a building whose frame is wrong. So I made the decision I would never have dared make at any earlier point in my writing life: throw away the published novel — keep only the facts — and write the story again from zero. New protagonist, new structure, new scenes. The first version is preserved on a branch of the repository, the way you keep the first pancake. Twenty days later, the ninth architecture became the book.

Understand what usually prevents this. It is not laziness; it is arithmetic. When a world costs a year of research to build, sunk cost sits in the room with you making your artistic decisions, and it always votes for the patch. What AI actually changed for me is not that it wrote anything — it is that it made *demolition* affordable. Rebuilding the world took days, so the only question left standing was the right one: is this the best book these facts can carry? Once that is the only question, the rewrite is not brave. It is obvious.

In June I said there were two things AI could not do: it cannot originate — its nature is to be mediocre at scale, a vast average of everything already written — and it cannot type the words that have to be yours. Thirty-nine days and two novels later I would add two more. The third I have already confessed: it cannot write natural language, only draft it — fluent in every language that has a compiler, a foreigner in every language that does not. The fourth is the deepest: it cannot want.

Nothing in the machine wanted this novel rewritten. Every agent in my editorial office was perfectly content with version one; the cold readers scored it and went back to sleep; no process anywhere raised its hand and said *this is not good enough, and I care*. The dissatisfaction that demolished the book — that read eight readers' letters and heard, underneath the typo reports, *the frame is wrong* — was not available at any price per token. It is still the only thing the author brings that nothing else can supply. It had better be, because everything else is getting cheap.

I once compared writing software to tailoring a coat — people see the outer cloth — and writing a novel to knitting a sweater, where every stitch stays visible forever. I stand by it, with an amendment. This time I unraveled the whole sweater, all seventy-some thousand stitches of it, and knitted it again because the first one hung wrong. The machine wound the yarn, held the pattern, counted the rows, and argued with me about the collar. It did all of that superbly.

It has never once wanted a sweater.

*Too Late* is on GitHub — Markdown, EPUB, and PDF: github.com/xiaolai/too-late. The first version is preserved on the `v1` branch. The second version is still being polished, which makes this exactly the right time to do what the first eight readers did: read it, and tell me where it's wrong.

Copyright: © LookMinds. Our own edited text and translation, not a substitute for the original; rights in the original belong to the author and the platform. Please see the original link.