Taste, written down and enforced.

The canon is version-controlled memory, and it is machinery, not notes. Each file exists to prevent one specific failure, and a fact that is not in the canon does not exist. You write the canon; agents obey it. Expect the design to take real creative work. It is the same work a novelist has always done, moved from the margins to the center. Two halves:

The story canon keeps the book coherent

• Premise lock. The decisions you will not revisit, written by you and supreme over everything else. Agents obey it; nobody edits it mid-book, including the machine, especially when it has a better idea.
• World bible. The rules of your world, each fact tagged load-bearing or decorative, so revision knows what it may touch. You decide which is which; that decision is worldbuilding itself.
• Character bibles and a knowledge ledger. Who knows what, when, and, separately, what they may reveal. A character can hold a secret from page one; any line that exposes more than their current ceiling is a logged leak.
• Reveal schedule. Information release as a scheduled resource: every secret pinned to a tier per chapter (trace, hint, suspicion, confirmation). You set the schedule; tension is engineered, not hoped for.
• Continuity ledger. Append-only: every fact the prose commits to gets an entry the moment it is written.

The taste canon keeps the book good

• A style spec with numbered rules, each anchored by a before/after pair you choose, so two editors reading it land on the same verdict. This is where your taste stops being a feeling and becomes law.
• An AI-tell blacklist: the machine’s habitual constructions, named and banned, every entry mechanically detectable, one hit fails the chapter.
• Count caps. Taste as a budget: how often the narrator may hedge, how many rhetorical flourishes a chapter is allowed. What can be counted can be enforced.
• A voice rubric and a voice anchor. Every chapter scored on named dimensions, with veto dimensions that sink a passage alone. Before the machine writes a word, write a page in your own hand, no AI. That page is the anchor every voice dispute comes back to, and only you can write it.

Two disciplines make the canon real rather than decorative. First, the canon is briefed, not dumped: the writer gets the synopsis, the current beats, and the canon entries that bear on this chapter. A rationed briefing, not the whole archive. Second, the canon syncs back: after every chapter, the new facts the prose created are written into the ledger before the next chapter begins. A canon that is only read drifts; a canon that is written back is law.

One model asked to write, remember, and judge will do all three badly, above all the judging, because the maker cannot grade itself. The room divides the labor into roles with opposed interests. Each agent role is the same machine under a different contract; the adversarial stance is the point. You are not a role in the room. You are the one it reports to, and the one who built it.

The method runs as two loops, and the first is the one that gets skipped. Skipping it is how slop gets its premise: a first idea, frozen by default, executed at scale.

The design loop ends in a lock

Before any prose exists, the premise runs a loop with you inside it. You state the premise; an interrogator with a mandate to refute attacks it: the engine that is a situation rather than a question, the ending you have not actually decided. You revise, it attacks again, in rounds. The Premise Gauntlet is this loop’s instrument, and the loop has only one exit: you lock the premise, in your own words, as the law of the book. This is the one place the machine may argue with the premise. After the lock, it obeys, especially when it has a better idea.

The production loop: every chapter earns its way out

Per chapter: write → audit → critique → revise, gated. The writer drafts. The continuity keeper audits against the ledgers. The critic scores against your rubric; a blacklist hit or a broken cap is an automatic fail. Revision addresses the notes, and the chapter runs again until it clears. You read what clears, and nothing ships that you have not read. Three rules keep the loop honest:

• Contested changes go to a blind jury. Two versions, provenance hidden, independent verdicts, including one juror primed to cut darlings. When the machine polishes a passage, the jury decides whether the polish survives. It often does not. Split verdicts come to you.
• Subtraction is a first-class move. Every pass tries deleting the weakest sentence. If the chapter survives, the sentence was decoration.
• The formulaic scene shape is banned: establishing description, then dialogue, then a reflective closing summary. When every scene has the same skeleton, the reader hears the template before the story.

The altitude problem

Per-chapter checks cannot see cross-chapter rot. Repetition of device, drift in voice, and continuity errors cluster in the middle of long books; each chapter passes alone while the book fails together. So the method audits at altitude: at every act boundary, run the ledgers across all chapters so far, and read the middle twice. Before release, the whole surface goes in front of eyes that have seen none of the making. These passes exist to find what the loop structurally cannot; when they do, that is the method working, not failing.

And once per book, check the checker: audit a chapter against the source chapters themselves, not the ledgers. An error that lives in both the prose and the canon will pass every check that compares them to each other. It happened to us.

The cold read: a stranger, in order

The last of those passes is also the simplest: one reader, cold. It receives a clean manuscript, body prose only, in a context that has never seen the project, and it takes the chapters strictly in reading order, because order is the thing no per-chapter gate ever sees. The cold reader does not grade and does not propose fixes. It keeps a ledger as it reads: the promises it believes it has been made, the devices it notices recurring, the doubts, the places its attention sagged. Wear is cumulative; only a reader moving in sequence can feel a device stop working. The Cold Reader Protocol is this pass, ready to paste.

Then put the ledger on trial. Cold readers file true and false findings at the same confidence; ours did. Verify every note against the text before you obey it, and only then rule it real. What proves deliberate, a choice the book made that reads as a mistake, goes into a do-not-fix register so no later pass undoes it; what stays unverified waits for a second stranger. The register matters as much as the fix list. It is how the book’s choices survive its audits.

When the same note returns, the fix is upstream

Some notes come back. You fix the line, run the pass again, and the note reappears two chapters later in different clothes: pacing that sags in every act, or the same close on chapter after chapter. A recurring note lives above the line, and line edits will not move it; five passes below the problem’s altitude proved that for us. It is the book telling you where its structure is thin. So go upstream, back to the canon, where the problem lives. Add the arc the book is missing, or give the antagonist the pressure the middle lacks; a device that repeats can be taught to mean its repetition. Then the new material faces the same critics and the same juries as everything it joins. The audits do more than catch defects: they are how a book asks for what it does not yet have. The best material in our first novel arrived exactly this way: late, after the whole-surface reads named what was thin, and it kept its place only by winning blind.

1. The premise survives its own loop and is locked, by the author, before the machine writes a word.
2. A fact that is not in the canon does not exist.
3. The canon is briefed, not dumped, and synced back after every chapter.
4. Information release is a scheduled resource.
5. A quality bar only works if it is numbered and anchored.
6. Name the machine’s tells and ban them mechanically.
7. The maker never grades itself; enforcement is adversarial.
8. Blind comparison beats self-justification.
9. Fix pacing in the outline; audit the book at act boundaries; read the middle twice.
10. Before release, a stranger reads the book whole and in order; the notes are testimony, verified before they are obeyed.
11. A note that survives two passes is structural; the fix lives in the canon, not the line.
12. The author designs the law, reads every verdict, and rules on every tie. Only execution is delegated.

Read everything above in the light of what it is: the shape the discipline took for one book, written down. It is deliberately unfinished. The ground here is too new for standards, and a framework would promise what nobody can yet promise: that following it produces a book worth reading. We make the smaller claim. Write your standard down, enforce it against yourself, and keep your own judgment in the chair; the rest of this page is one studio’s answer, published to be argued with.

So take the loops apart and rebuild them for your book. Add rooms we have not imagined; retire the ones that earn nothing. What survives contact with your pages, keep, and write down what you learned, because the writing down is the method. Everything else here is scaffolding, and scaffolding comes down when the book stands.

The method scales down. You do not need the whole room to begin. You need a written standard and one adversarial check.

• Five minutes: paste the Anti-Slop Prose Guard into whatever you already write with. That is the taste canon in miniature, enforced by self-check.
• One evening:design your canon’s first layer. Run your premise through the Premise Gauntlet until it survives. Then write the lock, one character’s bible, and five style rules with before/afters; the Story Canon Starter is the template. Specify the voice the same evening, anchor lines written in your own hand, no AI; use the Voice Spec. The only machine in the evening is the one refuting you; every word that gets kept is written in your hand.
• The book: run the production loop with the Adversarial Critic grading every chapter against your standard and the Blind Jury Protocol ruling on contested changes. When the last chapter clears, hand the book to a stranger: the Cold Reader Protocol is the last pass before release. You read everything that clears, and the ties are yours.