In This Article

Step 1: Establish Exactly What You Are Changing

You are revising a murder on an overnight train and decide to change who left the pocket watch at the scene.

In the original draft, it was Noel. In the new draft, it is Clara, a train attendant.

Changing a few lines in the ending is easy. But an earlier sequence is already in place: Erik lends the watch to Noel, Noel carries it into the victim’s compartment and leaves it there, and Eve, the investigator, later takes it.

Clara was originally in the dining car and never received the watch. Eve’s investigation and the ending were also written around Noel having left it.

This is not a new name for the same character. You are giving an existing action to someone else.

State Established by the Original Draft What the New Draft Needs Question to Resolve
Noel holds the watch. Clara leaves it at the scene. Where does she obtain it?
Clara is in the dining car at this point. She enters the compartment herself to leave it. Have you recorded the corresponding movement?
A witness says they saw Noel visit the compartment. Clara is now the person who places the watch. Does the statement still hold, or does it need a different explanation?
Eve’s knowledge condition concerns Noel leaving the watch. The ending requires her to identify Clara as the person who left it. Is there an information source for the new answer?

These questions give you a manageable scope for the revision. You do not have to recheck every passenger and subplot immediately.

InkWeave helps you start with the relevant events and states. Character locations, item holders, and explicitly defined conditions have sources you can look back at. You do not have to reconstruct your original plan entirely from memory.

You can begin with one part of the change. Work out how Clara receives the watch, then follow it through placement, discovery, and revelation.

Step 2: Update the Events, Not Just the Name in the Ending

You decide to keep Erik’s loan to Noel and add another transfer: before Noel leaves the dining car, he hands the watch to Clara, who is there with him.

After receiving it, Clara moves to the victim’s compartment and puts it down.

The new draft now has a sequence that supports the placement.

Event to Check Original Arrangement Choice for This Revision
Erik lends the watch. Transfers it to Noel. Keep it.
Noel hands over the watch. No such transfer in the original. Add a transfer to Clara in the dining car.
Noel visits the compartment. Originally connected to leaving the watch. Decide separately whether the new story still gives him a reason to visit.
Clara enters the compartment. No such movement in the original. Add the corresponding movement.
The watch is placed. Noel leaves it. Change the placement to Clara; do not retain Noel’s original placement as well.
Eve takes the watch. Acquires it from the compartment. This can remain after checking the new placement source.

Noel’s visit does not have to disappear simply because someone else leaves the watch. He may still have something to do there. You can keep the visit, give it a revised purpose, and make the witness’s observation fit the new version.

But you do need to deal with the original placement. Adding Clara’s placement while leaving Noel’s event for the same watch in place creates another source problem to check.

In InkWeave, adjust the relevant movements and item events to match what actually happens in the revised draft. The prose can still tell the story your way. Recording causality does not require turning it into a list of character actions.

Revision Note: Changing the Prose Does Not Automatically Change the Events

The Causality Engine calculates from explicitly recorded events. It does not infer from a new name in the ending that you want someone else to leave the watch. When an action changes in the prose, check the characters, items, and order in the corresponding events too. Unchanged events still contribute to the calculated state.

Step 3: Check the Revised State at Key Points in the Manuscript

After updating the events, stop at a few important points to check their results.

After Noel hands over the watch, Clara should hold it. After she enters the compartment, her location should change. After she puts the watch down, it should remain in the compartment rather than in her possession.

Point You Are Checking Clara’s Location Watch’s State
After the transfer in the dining car Dining car. Held by Clara; no longer held by Noel.
After Clara enters the compartment Victim’s compartment. Still held by Clara.
After Clara puts the watch down Victim’s compartment. In the compartment.
After Eve takes the watch Check against the movements recorded up to this point. Held by Eve; the same watch no longer remains at its original spot.

At different cursor positions, InkWeave’s Causality Engine derives the state from events confirmed before that point. The scene view and the character and location Inspectors can show the people and items present at that moment.

As you write about Clara, the watch, and the compartment, you can check those details in the relevant views. If you have added images for characters, items, and places, those can appear too, keeping the revision connected to a story you can see.

Interaction prompts can show current character and item states, then let you confirm whether a movement, transfer, or placement is needed. Names appearing close together do not make the engine decide what happened in the new version.

When you need to look back, character movement and item histories lead you to the relevant chapters and event positions. The state at a point shows what the revision has produced there; the history helps you trace its source.

You can alternate these checks with writing. Check a passage as you revise it. You do not need a complete new case before you can see any feedback.

State Note: Seeing an Item Later Does Not Mean Its Earlier Source Is Resolved

If a transfer leaves a quantity or source shortfall, later states may still show the item’s subsequent movements. Finding the watch in the compartment at the end does not establish that the earlier problem is fixed. Check the corresponding validation results and event sources as well.

Step 4: Trace the Sources Behind Validation Results, Then Choose a Fix

You can review this revision in two passes.

In the first pass, you change the person in the placement event to Clara but have not yet added her acquisition or movement. According to the current records, she is still in the dining car and has not received the watch.

The reminders now correspond to unfinished parts of the revision.

Result to Check Source to Review Possible Fix in This Case
Clara has no source of possession when she places the watch. The watch’s earlier transfers and quantity at that point. Add Noel’s transfer to her, or another valid acquisition.
Clara is still in the dining car but is meant to leave the watch personally in the compartment. Her location at that point and preceding movements. Add her arrival in the compartment, or redesign how the watch is placed.
The ending’s new knowledge condition has not been met. The events through which Eve learns the information and the corresponding flags. Arrange a new source, change the condition, or postpone the reveal.

Review validation results in the project-wide diagnostics dashboard, Project Seer. Use the relevant diagnostics, character movement history, and item history to trace their sources. Spatial diagnostics can also show the parties’ locations at that point, helping you see which part of the planned scene needs another look.

InkWeave’s Causality Engine is developed in-house and calculates states deterministically from explicit events and rules. Quantities, state transitions, and condition comparisons are handled through mathematical operations and defined rules, not AI guesses about whether the new draft is plausible. The same records and rules produce consistent state and validation results.

After choosing a fix, begin the second pass: add the dining-car transfer and Clara’s movement, adjust the original placement event, save, and review the new validation results.

There is no single prescribed answer. Clara could receive the watch from someone else, leave it at another location first, and have another person bring it into the compartment. Each choice creates a different sequence.

Reminders Do Not Take Over the Story

This version requires Clara to enter the compartment herself, so her movement needs checking. If you deliberately arrange a transfer across locations, you can confirm the exception. Unmet future conditions can also remain as writing tasks. You do not have to pretend every prerequisite has already happened just to clear a reminder.

Once the sources and locations covered by those checks are resolved, turn to another question: are the dialogue and investigation still using the old version?

Step 5: Reread the Testimony and Reveal, Then Validate Again

In the revised draft, Clara has received the watch, entered the compartment, and left it there. That item history can work without automatically completing Eve’s reasoning.

Eve originally checked Noel’s visit and placement of the watch. To identify Clara as the person who left it, she now needs information supporting the new answer.

Reread the relevant scenes. What did each witness see? Who is named in each record? Has Eve confirmed what happened, or is she proposing a theory?

If Noel still visits the compartment, the original eyewitness account can remain. But its continued existence does not make it proof that he left the watch. The new version may require Eve to reinterpret that account or find information that distinguishes the two characters’ actions.

Update the knowledge conditions too. A flag defined as “Eve has confirmed Noel left the watch” does not automatically become a different condition because the ending now names Clara.

Create or adjust the flags needed for the revision, set them where the information is actually confirmed, and have the ending’s condition gate check the corresponding prerequisites.

Condition Note: Passing the Old Check Does Not Support the New Answer

If the ending still checks the old flag, the engine uses its old definition. It does not understand the dialogue and replace the condition for you. When revising, check not only whether a condition passes, but also what it is checking.

While the new information source remains unwritten, an unmet condition can remind you what an earlier scene still needs. Once you add the source and corresponding events, review the new validation results.

Finally, reread the reveal. Does Eve distinguish confirmed facts from her inferences? Have readers had a chance to see the necessary clues? Does the scene mistakenly equate Clara leaving the watch with Clara committing the murder?

Those questions need your judgment of the whole case. The engine maintains explicit states and modeled prerequisites. It does not replace your reading of character motives, the meaning of testimony, or the quality of the reasoning.

Mystery Novel Revision Checklist

After an important revision, use the table below to review it. Start with the affected areas and widen the scope as you find problems. You do not need to recheck every record from the beginning each time.

Area to Check How InkWeave Can Help What You Need to Review
Character locations and timing Shows locations at a given point, provides movement history, and validates relevant spatial prerequisites. Whether clock times, travel, and scene order fit the case.
Evidence movements Checks holders, quantities, and transfer sources. Whether the revised acquisitions, deliveries, and placements make sense in the story.
Reveal prerequisites Checks explicitly recorded flags and conditions. Whether the conditions represent the information the revised draft actually needs.
Testimony and inferences Provides event and state records you can look back at. Whether observations, accounts, misunderstandings, and reasoning still hold.
What readers see Retains the world events you explicitly record. Whether necessary clues appear and the reveal has support.

You can also keep a short completion checklist for this revision:

  • Define the action, character, or result being changed.
  • Check the corresponding events, not just the prose.
  • Confirm how the new character obtains the item and reaches the location.
  • Update or remove events that no longer happen; do not accidentally retain duplicate placements or transfers.
  • Review relevant statements and distinguish direct observations from inferences.
  • Confirm that flags and condition gates check the prerequisites the revised draft needs.
  • Reread clue introductions and the reveal, checking what characters and readers have each learned.
  • Save and review the new validation results, with a clear plan for anything still unfinished.

This checklist is your review tool, not a feature that lets InkWeave automatically check off every narrative task. Let the Causality Engine validate the states and prerequisites it can calculate. Reread the parts that require understanding the prose and the case yourself.

If you are starting from scattered notes without earlier event records, begin with the most important item or movement in this revision and build gradually. InkWeave cannot know events you never recorded. But you do not need to model the whole novel before checking a short sequence.

To try one revision pass, follow the Quick Start Guide to record a character movement and an item transfer. Then change one event and see how the state and validation results change. For downloads and available plans, see InkWeave Plans and Pricing.

The hardest part of revising a mystery novel is often not finding a better ending. It is making the earlier events genuinely support it.

Define the change, update the events, check the revised states, then trace and reread the affected scenes. Step by step, you can see which earlier events still hold, which later passages need a new source, and which part of the story the revision still needs you to write.