Keep every thread.Even the quiet ones.

The subplot you forgot

Most dropped threads aren’t abandoned. They are postponed: you meant to come back to the sister’s debts after the battle, and the battle took six chapters. By the time you look up, the reader hasn’t heard about the debts for forty thousand words. When the thread finally returns, it has lost its tension, or worse, it never returns at all and the reader is left wondering.

The usual fix is a spreadsheet: chapters across the top, subplots down the side, a mark in each cell where a thread appears. It works, and it is how many published authors plan. But it has to be kept up by hand, and it only shows that a thread appeared, not whether it moved.

How many threads a book can carry

There is no fixed number, but every thread costs the reader attention. A tight thriller might carry the main plot and one or two subplots. An epic fantasy with several viewpoints might carry a dozen. The test isn’t the count: it is whether each thread is moving often enough that the reader still cares when it returns, and whether each one eventually touches the main plot.

A useful habit is to ask, for every thread, what it is for. A romance subplot might carry the theme; a rivalry might raise the stakes of the climax; a mystery in the background might pay off in book three. A thread that carries nothing is a candidate for cutting, and one that carries a lot but appears rarely is a candidate for more scenes.

Threads also need endings. Readers forgive a lot, but a subplot that simply stops feels like a promise broken. Closing a thread can be as small as a line of dialogue, as long as it is on the page.

Threads that know how they stand

In Authrot a thread is a storyline the readings follow. When a chapter is read, each thread it touches is recorded as opened, advanced or closed there, tied to the passage that did it. The story map draws every thread down every chapter, so the braid of your book is a picture rather than a memory.

Because each step is recorded, the map can tell a thread that turns in this arc from one that has gone quiet. An open thread with nothing since chapter five reads as quiet since chapter five, and quiet ones are flagged. A closed thread stops asking for attention.

A thread can also be the home of promises. The clues of a mystery subplot or the debts of a rivalry can hang on its thread, so the storyline and the setups it owes the reader are kept together.

• Opened, advanced and closed, each tied to its passage
• Quiet threads flagged on the story map and on each arc
• Threads span every book in a series
• Flashbacks follow story time, not reading order

Reminders: decide where it comes back

Knowing a thread is quiet is half the job. The other half is deciding where it should return. Each thread can be opened on the board, where your arcs are laid out with their beginning, middle and end and the stretches between. Click the stretch where the thread should come back into focus, and a reminder sits there: bring it back here. It is your best guess, marked where you will see it.

Reminders are loose on purpose. They mark a stretch of chapters, not a single line, so you have room to find the natural moment. Take one off with a second click, or clear them all and place them again.

Reminders work for promises as well as threads, on the same board. A promise or thread that has paid off, closed or been dropped still shows there, so you can see its whole life, but it has nothing left to remind you of.

Weaving a thread into a written chapter

Sometimes the right place for a thread to return is a chapter you have already written. Open that chapter on the board and Weave asks the AI for a short passage that brings the thread back there, placed after a specific line, with a note on why. It never edits the chapter directly: the passage waits as a proposal you add or drop.

The same works for promises. A setup that has gone too long without being mentioned can be picked up the same way, so the payoff later doesn’t come out of nowhere.

A woven passage is a starting point, not a verdict. It is usually best as a few lines that remind the reader the thread exists, which you then rewrite in your own voice. If a thread needs more than that to come back, it probably needs a scene, and that belongs in a chapter plan.

Threads and the cast

Subplots are usually people. The romance goes quiet because the love interest left the page; the rivalry fades because the rival hasn’t appeared since the tournament. Screen time shows the whole cast across every chapter (who is present, whose point of view, who exits), and characters who have been absent too long are flagged as due back.

Read together, the two views explain each other. A quiet thread next to an absent character tells you what to do: bring the character back, and the thread comes with them.

Connections adds the ties between them. A rivalry thread lives in the relationship between two people, and the web shows who is tied to whom at any chapter, as a web of the whole cast, a circle, or everything around one character. When a thread goes quiet, the people it belongs to are a click away.