Taste, written down and enforced.

Version-controlled memory, and machinery: each file exists to prevent one failure. A fact that is not in the canon does not exist. You write it; agents obey it. Expect the design to take real creative work, because it is the authorship, done before the writing.

The story canon keeps the book coherent

1. Premise lock. The decisions you will not revisit, supreme over everything else. Nobody edits it mid-book, the machine least of all.
2. World bible. Every rule tagged load-bearing or decorative, so revision knows what it may touch.
3. Character bibles and a knowledge ledger. Who knows what, when, and what they may reveal. A line above a character’s ceiling is a logged leak.
4. Reveal schedule. Every secret pinned to a tier per chapter: trace, hint, suspicion, confirmation. Tension is scheduled.
5. 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

1. Style spec. Numbered rules, each anchored by a before/after pair, so two editors land on the same verdict.
2. AI-tell blacklist. The machine’s habitual constructions, named and banned. Every entry mechanically detectable; one hit fails the chapter.
3. Count caps. Taste as a budget: how often the narrator may hedge, how many flourishes a chapter gets. What is counted can be enforced.
4. Voice rubric and voice anchor. Named dimensions with vetoes, and a page written in your own hand before the machine writes a word. Every voice dispute ends at that page.

Two rules that keep it law

1. Brief it. The writer gets the synopsis, the current beats, and the entries that bear on this chapter, never the whole store.
2. Sync it back. After every chapter, the facts the prose created go into the ledger before the next chapter begins. A canon that is only read drifts.

One model asked to write, remember, and judge does all three badly, the judging worst, because the maker cannot grade itself. So the labor is divided into seats with opposed interests, each the same machine under a different contract. Your seat is outside the room. It reports to you.

The first loop designs the book and ends in a lock. The second builds it a chapter at a time, and is the only one where execution is delegated. The third reads the finished book whole and sends what it finds back upstream, so the three run as a circuit. On our first book the return path carried most of the work: fifty-four commits after the last chapter was accepted, against thirty-seven to draft them all.

Loop one · Design, until the premise holds

1. State the premise, the kind of book, and the form of the telling.
2. Let an interrogator with a mandate to refute attack it, one test at a time. The Premise Gauntlet is the instrument.
3. Rework, and rerun every test the change touches.
4. Write the voice as mechanics anyone can check: where the verb sits, how a paragraph lands, budgets that are counted, anchor lines in your own hand. Rule zero is no author names, because a name cannot be checked against the prose. The Form and Genre Lock and the Voice Spec hold this.
5. Lock it, in your own words. This is the only place the machine may argue with the premise. After the lock it obeys.

The lock settles three things that cannot change at chapter twenty without a rewrite: the premise; the kind of book, meaning what it promises on the first page, owes by the last, and refuses to be; and the form of the telling, meaning who speaks, from what distance, knowing how much. Ours is one man’s retrospective account, set down two years after the events by a narrator arranging his own defence. That one decision fixed the tense, the withholding, and the terms on which the ending could land.

Loop two · Production, every chapter earns its way out

1. Brief. One chapter brief: what the chapter is for, the reveal it may deliver, whose certainty moves, the question it ends on. No brief, no draft.
2. Draft. The engine reads the whole canon first and heads the draft with every fact it commits to.
3. Count. The tally does the counting exactly. A model is the wrong instrument for a count.
4. Audit. The continuity audit checks the declaration against the canon and the prose against both. Clean, or back to the writer.
5. Grade. The critic scores against your rubric and never writes a line. A blacklist hit or a broken cap fails the chapter.
6. Accept. You read what clears. Nothing ships unread.

Three rounds is the ceiling. A chapter still failing after three has a design problem, and design problems go upstream to you. The runbook gates the cycle: fresh context per seat, one owner per file, and the grader never sees the writer’s conversation. On The Archivist the room was literal, with writer, auditor and critic as separate agents.

This loop’s unit is the chapter, and that is its ceiling. What exists only across chapters belongs to loop three; running this one harder will not find it.

Loop three · Refinement, the book whole and in order

Every chapter can pass and the book still fail. Wear is cumulative, drift is gradual, and a promise made in the first act comes due in the fifth. Per-chapter gates see none of it, so this loop takes the whole book as its unit and reads it in order. Three instruments:

1. The cold read. A clean manuscript into a context that has never seen the project, chapters in reading order. It grades nothing and fixes nothing. It keeps a ledger of promises, recurring devices, doubts, and where its attention sagged. The Cold Reader Protocol is this pass.
2. The panel. Several agent readers of the finished book, in different seats, reporting independently. What three find without conferring is the report. The Panel Protocol runs it.
3. The blind jury. Any contested change goes to independent verdicts with the provenance stripped, one juror primed to cut darlings. The Blind A/B Jury Protocol runs it.

Then adjudicate. The ledger is testimony, and readers file true and false findings at the same confidence. Verify each note against the text and rule it real (fix it), deliberate (the book’s choice wearing an error’s costume; it goes in a do-not-fix register so no later pass undoes it), or unverified (a second stranger reads before you act). One read per stranger.

Rules that stop the third loop eating the book

1. The incumbent is the control. A refinement draft never overwrites the chapter it replaces. The original is the other half of the comparison.
2. New material faces the old gates. Anything this loop adds runs production and then wins blind against what it displaces, or it does not go in. A restructure of three whole acts was drafted this way for our book and never promoted.
3. A recurring note is structural. When the same note returns two chapters later in different clothes, line edits will not move it. Go upstream into the canon: add the arc the book lacks, give the middle its pressure. The best material in our first novel arrived this way, late, and kept its place by winning blind.
4. Check the checker, once per book. Audit a chapter against the source chapters instead of the ledgers. An error that lives in both prose and canon passes every check that compares them to each other. It happened to us.

Trade publishing calls most of this the developmental edit. The difference is that this one loops: it changes the law upstream, and the chapters the change touches go back through production.

A framework would promise that following it produces a book worth reading. Nobody can promise that yet, so 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. Take the loops apart, rebuild them for your book, and write down what you learned. The writing down is the method.

The method scales down. 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. The parts only your hand can write. Run your premise through the Premise Gauntlet until it survives, write the lock, and set down the anchor lines yourself in the Voice Spec. The only machine in the evening is the one refuting you.
• The book. Finish the canon’s first layer on the Story Canon Starter, brief the first chapter, and run the loop as the runbook gates it. When the last chapter clears, hand the book to a stranger with the Cold Reader Protocol. You read everything that clears, and the ties are yours.

Or point your agent at the install first. It builds the whole room in a minute, and the evening stays yours.