AI Keeps Forgetting Your Novel? Track Characters and Plot
Oh Story · Updated 2026-10-15
AI drifts over a long novel when the model is asked to remember the whole book. Oh Story keeps the state in files instead: what is true in the story, what each character knows and what the reader has seen are recorded separately in the project's tracking directory, and each new chapter reads the current state, relevant prior material, its outline and promises not yet paid off. Anything still in the plan stays in the plan until the chapter that shows it is written. The three-chapter example below shows how the state carries from one chapter to the next, plus an optional clue design that separates a visible clue from a plausible misreading and gives the reveal consequences. The method targets two failures in particular: forgetting, and characters knowing answers too early.
Method fromstory-long-write11 method files
Before you start
- Use the same book project, with its actual completed chapters and tracking state. If an older manuscript has not yet become a continuable project, start with import and continuation. This guide covers keeping an existing project on track; one import is enough.
- Keep the chapter being planned, the last completed chapter and any partial draft distinct. In the example only chapters 1–2 are established; chapter 3 is still a proposal.
- Provide author-only decisions explicitly. A private answer guides the author; characters learn it only when a written scene gives them the evidence. Keep an unsupported guess from the model marked unresolved.
Steps
- Separate identity from the latest state Read the relevant
设定/角色/{角色名}.mdfor stable characterization and追踪/角色状态/{角色名}.mdfor current location, goal, relationships, knowledge and open threads. “Xu Tang has an older brother” and “Xu Tang knows he sent this letter” are two separate entries; the second goes into her knowledge only after a written scene gives it to her. Bring a returning character back from the latest state and leave the first-appearance introduction in the settings file. When the facts are consistent but a decision still feels out of character, the fix is motivation work: use character motivation to examine the reason and the change of tactic. - Use three information perspectives For each important secret, ask separately: what is the author-confirmed truth, what can each character act on now, and what has the reader been shown? The tracking transaction distinguishes
objective_factfromreader_knowledge; character knowledge has its own snapshot. Author-only answers and planned reveals stay outside what the current viewpoint character knows. - Carry a small, relevant handoff The continuation workflow checks the committed chapter, reads
追踪/上下文.md, this chapter’s blueprint and the relevant outline/character material. The context card includes current position, long-term constraints, character state, active clues, recent chapters, next-chapter commitments and continuity risks. When the card falls short, query older material directly; chapter logs load only as needed. These are required workflow steps; check that your agent actually ran them before it drafts. - Distinguish a story promise from the next writing task Xu Tang’s promise to deliver the letter before seven is an unresolved story obligation with a deadline. The chapter-3 handoff is to find a checkable old address without revealing the sender. A future chapter-4 reveal belongs in the plan and counts as delivered once chapter 4 is written. Keep
next_chapter_commitmentsto what the next chapter must carry: longer-range plans stay in the volume and chapter outlines, and a character’s standing vow goes in when the next chapter has to act on it. - Separate the open question, the clue and a possible reading “Will she deliver the letter before seven?” creates an expectation about a future action. The blue triangle is an observed detail whose meaning may matter later. “The clerk is hiding the sender” is one possible interpretation that no scene has confirmed. For this limited-viewpoint example, preserve the visible detail while leaving room to revise the interpretation; do not label it a secret sign in neutral narration and later pretend that certainty belonged only to the reader. The bundled suspense reference distinguishes questions and planted clues; these editorial distinctions are for planning, and the tracking fields stay as they are.
- Let evidence change knowledge before recording a payoff Finding a blue mark and knowing what it means are two separate events. Before declaring a clue resolved, show who obtained what evidence and which uncertainty it actually closes. After the chapter is written, have the existing chapter transaction update the result, affected character snapshots, clue state and reader knowledge to match the prose. Record a planned discovery in tracking only after its scene is written.
- Make the answer change the next decision A useful local payoff can settle one question while leaving another alive. In the proposed extension, a matching record can explain the triangle and identify the sender, but the delivery is still unfinished and the clock has advanced. The new address gives Xu Tang a route to choose; the promise is still hers to keep. This is one design option: whether to add a twist, and over how many chapters, is the author’s call. If the answer changes nothing in this story’s action, relationship or expectation, decide why it needs this much buildup.
- Keep one tracking authority
追踪/_tracking-state.jsonis the structured authority.上下文.md, character snapshots, clue views and author/reader timelines are derived outputs rebuilt from it, so every story change goes through the transaction. The workflow submits one structured transaction throughtracking_commit.py; ask the agent to show the resulting handoff, and treat a bare “I will remember” as a missed step. The card in the example below is for illustration; the real format is the transaction the workflow defines. - Repair old-chapter changes through their consequences If you remove or change the clue in chapter X, request a scoped chapter revision with the intended fact and affected passage. The documented revision path recalculates tracking from X through the last written chapter and lists later prose that may depend on it for you to check. Later chapters change only where you decide. Preserve current work before a large revision and decide which dependent passages should change.
Example
Example
ORIGINAL EDITORIAL EXAMPLE — The Returned Letter Authored excerpts and a planning card, written for this guide. Tracking JSON and chapter files come from your own project.
Established in chapter 1, at 18:20: Xu Tang slips an unopened returned letter into her inner pocket. “Before seven, I will put this into Aunt Shen’s hands.”
Established in chapter 2, at 18:35: The clerk covers the page corner with a finger. “This page only records returned items. The sender’s name isn’t on it.” Xu Tang sees a blue triangle beside the date. The envelope is still sealed in her inner pocket.
Author-only decision: Her older brother sent the letter; the triangle relates to a changed address. The author plans evidence-based confirmation in chapter 4; chapter 3 keeps it hidden. This is approved background that only the author knows so far.
Handoff before chapter 3 (plain-language labels for illustration): - Character knowledge: returned letter; blue triangle; sender still unconfirmed. - Reader knowledge: the same visible facts; no reveal of the brother as sender. - Prop/location: sealed letter remains with Xu Tang at the returns desk. - Unfinished story obligation: deliver it to Aunt Shen before 19:00. - Next chapter’s job: obtain a checkable old address and a next action. - Still withheld: sender identity and the triangle’s confirmed meaning. - Planned future event: chapter 4 confirmation; the payoff is still open.
Bad continuation: “Xu Tang recognized her brother’s forwarding mark. With the letter delivered, she decided to wait for him at the pier.” Why it breaks continuity: she gains two answers without evidence, and an undelivered letter becomes delivered without a scene. An intention is mistaken for an event.
A permitted opening revision (the first lines only): Xu Tang took out the still-sealed letter and laid it beside the register. “Is this triangle something your office draws when a letter comes back?” She checked the wall clock. Twenty-five minutes until seven.
If chapter 3 later establishes the old address, record that new knowledge after the scene is actually written. The triangle can remain unresolved; a new lead is progress, and the sender and the delivery promise stay open until later scenes settle them.
OPTIONAL CHAPTER 3–4 DESIGN — author choices for a possible continuation; everything here is proposed, and only the excerpts above are established. The returns desk and its records are invented for this story world.
Before drafting, approve these new conditions: the fictional office keeps a separate dispatch record, retrievable by a number on the envelope; it records the sender and a change to Aunt Shen’s recipient address. The record and notation key are kept in a back archive room, so the clerk must leave the desk to look them up by envelope number. The triangle belongs to an older register’s notation that the present clerk has to look up before saying what it means. In this branch the record is accurate and belongs to this letter. Introduce these conditions through the scene itself; the earlier excerpts are silent on them. If the story instead allows forged or mistaken records, finding a name proves only what the record says, and confirmation needs more work.
1. Chapter 2, already visible: the clerk’s finger covers a corner and a blue triangle sits beside the date. Xu Tang could suspect that the clerk is protecting someone. That suspicion may be voiced as a question; “the clerk was concealing her brother’s name” would leak an answer and assert a motive the scene has not established. 2. Chapter 3, proposed, 18:40: the clerk checks an old-address directory and gives Xu Tang an old address to verify. When asked about the triangle, the clerk says that this is an older register and its notation needs checking; this directly answers why its meaning is not being asserted yet. The clerk points out the envelope number and offers to retrieve the separate record and the old notation key. Xu Tang asks for that check, choosing to spend part of her remaining time confirming the destination while the old address waits. The clerk goes to the archive room; she waits at the desk. This prepares an evidence source and a concrete next action before the reveal, while the sender, the new address and the triangle’s confirmed meaning stay hidden. Copying an old address is progress; delivery needs a handover. 3. Chapter 4, proposed, 18:45: the clerk returns from the archive room with that record and the old notation key. Xu Tang compares its number and recipient with the still-sealed envelope. Its recipient-address-change entry carries the same blue triangle and gives Aunt Shen’s new receiving address; the key identifies the triangle as a recipient-address-change mark. Xu Tang reads it with the clerk. The separate sender field names her brother. The record’s accuracy is an approved premise of this branch only. The triangle explains the recipient-address status; the brother’s name comes from the sender field. The earlier statement that the returns page has no sender name stays true. 4. What changes: Xu Tang now has Aunt Shen’s new receiving address and, under the approved evidence conditions, a confirmed sender. The envelope remains sealed and with her at the desk. At 18:45 she has fifteen minutes left of the original twenty-five. Choose and establish a reachable route before promising success. A possible next action is to ask directions and leave for the new address; mark the letter delivered only after a handover is actually written.
Fair misdirection versus an unsupported answer: • Keep: a character wonders whether the covered corner hides a name, then checks, treating the guess as a guess throughout. A later view of the page can show its ordinary return fields. That can undercut the suspicion; the clerk’s wider character and motives stay open. • Avoid: reveal that the triangle is a private family code never available to the viewpoint or reader, or introduce an all-knowing record only in the answer paragraph. If you want either mechanism, go back and build it into the earlier setup so it really was there all along. • Do not stall with a repeated question alone. Chapter 3 obtains an old address and initiates a specific record lookup; chapter 4 changes knowledge and the available destination. The remaining delivery question can carry the next scene by itself, with no fresh villain or extra secret needed at every ending. The timestamps track elapsed story time, and chapter length is your call: if the lookup cannot support a meaningful chapter on its own, combine the scenes and keep the wait short.
Planning check for discussion: observed detail → current interpretation → needed evidence and its prepared source → what the answer changes → what remains unresolved. Use it to discuss this one clue before drafting. Only update actual clue and reader-knowledge state after the selected scenes have been written.
Read-only handoff request for an agent in the existing book project: Before drafting, show the actual last committed chapter and the next blueprint. For the involved characters, separate author truth, character knowledge and reader knowledge. List the current letter/prop state, unresolved clues, deadline and the next chapter’s specific commitment. Identify the source chapter or author decision for each; keep unknowns unknown. Do not draft prose or hand-edit tracking yet. After I settle the direction, I will explicitly request the chapter.
If revising an earlier chapter: “I am changing the blue triangle in chapter 2 to a torn corner; keep the sender unrevealed. Show which later references and planned reveals depend on the triangle, use the existing revision workflow for tracking, and do not rewrite later prose outside the scope I specify.”
Expected files
- A small, source-backed continuation handoff for the next chapter: current character state, relevant facts/clues, obligations and reveal limits. It works alongside the actual chapter blueprint and uses the existing tracking files.
- After a completed chapter, updated structured tracking and derived views that agree with its actual events.
追踪/上下文.mdholds the current handoff only. - For a past-chapter change, the revised prose plus a recalculated tracking state and an explicit list of potentially affected later chapters. Future manuscript edits remain separate scope decisions.
- If the problem is only formulaic wording, use prose revision and leave the plot ledger untouched.
Check the result
- Read the proposed paragraph from the viewpoint character’s position: did they obtain the knowledge they use, are props and location consistent, and has a promised action really occurred? Correct these before accepting a smoother sentence.
- A chapter can advance a clue and leave it open. The payoff counts once the prose delivers it to the reader; planning dates, future reveal numbers and passing state checks record the plan and its consistency.
- For a planned payoff, can you point to an earlier observed detail, a prepared way to check it and the decision that changes after the answer? Keep a character’s mistaken interpretation distinct from established narration. Use the fiction-analysis exercise when you need to separate text evidence from your reading.
- The cited workflow makes state explicit and describes transactional updates. Characterization, voice, suspense and long-run accuracy still need your own read-through.
Sources
- Continuation inputs, state card and next-chapter commitments
- Load only the relevant current state
- Static characters, current snapshots and revision cascades
- One tracking authority and derived views
- Author facts, reader knowledge, clues and commitments
- Read surrounding chapters before revising
- Recalculate tracking and identify affected later prose
- Future outlines stay separate from established tracking facts
- Questions, planted clues and plausible misleading hints
- Chapter movement through evidence and a local state change
- Current workflow source (2026-10-15)