Revision

The four-pass model

• Pass 1, structural.Are scenes earning their place? Does the spine hold? Should chapters move, merge, split? Don't fix prose; you may cut it.
• Pass 2, character. Is each character distinct in voice, motivation, arc? Are minor characters doing more than one thing? Cut anyone redundant.
• Pass 3, line.Sentence-level prose. Cut filler. Tighten rhythm. Fix continuity. This is where the “polish” comes in.
• Pass 4, proof. Typos, formatting, consistency. Read aloud or use text-to-speech.

Don't mix passes

The most common revision failure: the writer is doing pass 3 (sentence-level prose) on a manuscript that still has pass 1 (structural) problems. They polish a chapter into beauty and then have to cut the chapter. Don't fix what you might cut.

The cooling-off period

After finishing a draft, set it aside for at least two weeks before revising. Six weeks is better. The first time you re-read it, you want to be reading it as a stranger would, not as the person who just wrote it.

What Pendraic surfaces during revision

• Iterations layer, track passes, attach findings, mark scenes as locked vs. open. The closure ledger captures decisions you don't want the AI to re-litigate.
• Voice conformance reports, running scans against your Voice Print catch drift you'd otherwise miss in your own prose.
• Penny's revision tools, ask Penny to run a structural pass, flag pacing issues, identify scenes that don't change state. The full PENDRAIC context bundle gives her enough to give you specific, grounded notes.
• Beat anchor audit, every Engine beat should be anchored to a scene by the time you're done with pass 1. Unanchored beats mean the spine isn't complete.

When you're done

Books are never finished, only abandoned. Pick a stop condition before you start: “After three full passes and a beta read, I ship.” Otherwise revision becomes a coping mechanism for not submitting. The third pass is usually 80% of the value; passes four and beyond are diminishing returns.