Pantheon

Vivienne Ho is a socialite and a financier in Hong Kong, principal of a firm that buys businesses other people would strip and keeps them alive. She has spent five years building that life so completely it became real to her. Damien Tang wants to marry her, and his family runs due diligence on the woman he has chosen in the same season an old institution reopens a file on her.

Finished: all 63 chapters, 152,889 words, close third, past tense, rotating point of view, published 1 November 2026. After the first full edit I reopened it on 22 September and rewrote and edited it myself from chapter one forward. The editing ran as ordered levels, structure before line before copy before proofread, on the principle that polishing a sentence you are about to cut is wasted work. That word count is not asserted anywhere: it is the sum of what the sixty-three chapters each declare, and the linter fails on any chapter that disagrees with the count it just took.

Pantheon is the first of three. Circe and Damien carry all of them and each book gets its own antagonist. The second has its beat sheet blocked end to end at 60 chapters and four of them drafted. Book one ends on its own terms; I did not hang a cliffhanger on it to sell the next one.

Chapters 1 to 7 are free in the web reader, with adjustable type and a serif toggle. That is the end of the third sequence, not an arbitrary stopping point.

The ebook came out on 1 November 2026, on Kindle, and it is in Kindle Unlimited from the same day. A new book with no reviews asks a stranger to pay for a name they have never heard; a borrow asks them for nothing, and borrows still count toward the rank that decides whether anybody else ever sees the book. Kindle Unlimited pays by pages read, so a 153,000-word novel earns roughly what a sale does instead of being a pricing problem. Exclusivity runs in 90-day terms, so it is a decision I can take back. The paperback and hardcover came out the same day. The website is a free sample and is never required reading.

The files uploaded when the pre-order opened carried the pre-read-through text and a cover two generations retired. Every destination was rebuilt from the finished manuscript and uploaded again before release, so what arrived on 1 November was the edited book rather than whichever draft happened to be current in August. A pre-order is a promise made months before anyone opens the file.

The site does one thing: it lets you read the first seven chapters free, then decide. A spoiler-free novel page with the premise, the two leads and where to buy, a reader built for the sample, and a press kit for reviewers. Nothing on it runs ahead of those seven chapters.

Adjustable type size and a serif toggle, both remembered on your device. Finishing a chapter marks it as your furthest and offers the next one. No account, no email, no analytics, and your progress never leaves your browser.

Five static HTML pages, plain CSS and classic scripts. No framework, no bundler, no dependencies, no lockfile. One Python script writes the image derivatives and the sample chapters; everything else is hand-written, and every behaviour is client-side.

The screens were designed on a dark navy theme and ship on a different one, carbon and brass and proof red. The second is an override layer rather than a rewrite: delete one link tag from five pages and the site is the first palette again, exactly.

Every text node was walked against its real composited background rather than eyeballed. Seven pairings failed AA and are fixed. Six of them had been failing on the original palette and had simply never been checked.

A single field, publishedThrough, decides what a stranger can read. It cuts the served chapter text and every sentence of site copy that names a chapter count. Raising that number is the only thing that publishes a chapter.

Chapters past the sample are never copied into the site folder, so they are missing from the deploy rather than filtered in the browser. Manuscript frontmatter is stripped at build time for the same reason: a field that names something the book reveals later cannot be hidden at read time, because hiding it still ships it.

The asset build reads the directory, not its own list. Removing the last link to an image does not remove the image, and it stays live at its address for anyone who has it. So anything on disk that the build did not declare is a failure rather than a leftover.

Forty-eight scripts. A prose lint per chapter, a cross-chapter voice-drift report, a citation checker that re-reads every quotation canon claims, a POV brief that answers what this head is allowed to know, and a pass that strips the narration so the dialogue can be read as a script.

260 cases, all passing, each one a bug the tools once missed. Every tool here was built reactively, one fault at a time, so the fixture file is the record of what they used to let through.

About 104,300 words and 309 numbered lessons, sorted into nine families of mistake. Adding to it is part of fixing anything, otherwise the fix applies to one chapter and nothing else.