Write first.Map it later.

Discovery writing has a bill, and it arrives in revision

Writing into the dark is a real method, not a lack of one. Plenty of novelists only learn what the book is about by drafting it: the villain’s reason surfaces in chapter twelve, the twist arrives because a character said something unplanned. That freedom is the point. The cost is paid later.

By the end of a discovered draft, nobody, including the author, has a clear record of what happened. A name drifted from Marek to Mareck. A sister was mentioned once and never again. Three clues were planted by instinct and only one paid off. The revision pass becomes archaeology: rereading the whole book with a notepad to reconstruct the story you wrote. That’s the part a studio can take off your hands.

Most writing tools are built for the other camp. They open on a corkboard, a beat sheet or a character questionnaire, and they work best when the cards are filled in before the chapters. A discovery writer either fights the tool or ignores it, and ends up back in a plain document with a notes file that is out of date by the second week. What a pantser needs is a tool that does its work after the writing, not before.

Write first. The bible follows

Authrot never asks for an outline. Open a project, choose “Write it myself”, and type. When a chapter is done, have it read into the story bible: the characters, creatures, places, items, factions and lore it mentions each get an entry, and every reference is recorded, from a name spoken aloud to a scene that relies on someone who never appears.

If you’d rather not stop to ask, reading can be set to happen automatically after you stop typing. If you’d rather not use the AI at all, link names by hand by typing [[ or selecting a name; it’s free and works with the AI off. Near-duplicate entries are caught when chapters are read, and merging two moves every reference with them, so the Marek and Mareck problem is fixed in the bible and in your prose at once.

• Entries made from the text, with importance from main to once
• Rename an entry everywhere in the text, with a preview and undo
• Close-spelling search for the name you half remember

A map of the book you actually wrote

A plotter’s outline says what should happen. A discovery writer needs the opposite: a record of what did happen. The story map draws every plot thread down the chapters, so you can see that the smuggling subplot vanished after chapter nine, or that two threads you thought were separate keep landing in the same scenes.

Promises are the questions you raised for the reader, whether you meant to or not. The map groups them as due now, left hanging, or the long game, and you can ask of any one whether it has paid off, is still being carried, or was dropped. Contradictions are flagged against the earlier line they break, which matters most for a writer who changed their mind about the world halfway through.

Screen time shows the cast across every chapter: who is present, whose point of view a chapter is in, and where each character exits. For a discovered draft this is often the most revealing view of all. It shows the narrator who disappears for six chapters, the antagonist who is talked about but never on stage, and the minor character who turned up in every scene because you liked writing them, which may be the book telling you something.

When the notes pile up faster than the chapters

Discovery writers often keep a sprawl of notes: alternate openings, three versions of the main plot, a scene written at midnight for a book that might not exist. “From your notes” reads that pile and finds where it fits. It shows the storylines the notes suggest, each with quotes from the notes it came from, and calls out where one conflicts with a chapter you’ve already written.

You review them side by side and use the one you like, or mix parts of several. Nothing in your plan changes until you finish the review, and History can undo it. For the everyday mess, ✦ Organize the project refiles notes, orders and titles chapters, and folds notes into bible entries. It never rewrites your text, and it can be undone.

Follow the fork without losing the road

The hardest moment for a discovery writer is the fork: the story could go two ways and you won’t know which is right until you’ve written some of both. Branches let you do exactly that. Start a branch from everything so far, or rewind to after any chapter and take the story somewhere new, with the bible cleaned of everything that no longer happened.

For a single scene, keep alternate takes of one chapter side by side and choose the one the book uses. When a branch wins, merge it back: you see what will change first, and you’re asked about each real conflict. The road you didn’t take stays in History, in case chapter twenty proves you wrong.

Planning after the fact, if you want it

Some pantsers never outline. Others find that once the draft exists, a plan finally helps, because now there’s something true to plan around, and the second half of the book can be written with the first half’s shape in view. The “Bring a draft” way in reads what you’ve written and lets the Co-writer draft the open Foundations steps from it: the core, the voice, the cast, the world.

From there the Arcs page sets goals, opposition, stakes and turning points for the arcs your draft already has, and drift checks tell you when a chapter strays from its arc. Anchor the decisions you’ve settled and the AI never redrafts them. You stay a discovery writer; you just stop paying for it in revision.