Both journeys end at East Camp, but their histories differ

You open two versions of a story.

In both, Nora the courier has reached East Camp.

The supplies have been delivered.

The mountain pass has been destroyed.

Looking only at the latest results, the two timelines seem almost identical.

But when you return to Nora’s journey, the difference becomes clear.

In Path A, Nora crosses the mountain pass first. It collapses in a later disaster, after she reaches East Camp.

In Path B, the pass is already destroyed before she sets out. You send her along the river route instead, and she eventually delivers the supplies.

The same character.

The same destination.

Even the same final state of the mountain pass.

But not the same history.

If you remember Path A’s successful crossing while writing Path B, you may send Nora into a route that no longer exists in this version.

The problem is not a missing map.

You are using another timeline’s event order.

Organizing a novel timeline means tracking more than what happened. It also means knowing what the world was already like when each event took place.

Put each journey’s actual events in order

You don’t need a chronology stretching from ancient history into the distant future to organize this journey.

A few events that affect one another are enough to reveal the difference.

Nora acquires the supplies.

She enters a location.

She reaches East Camp and delivers them.

The mountain pass is destroyed.

You establish the river route as another way forward.

Event order Path A: Pass crossed first Path B: Pass destroyed first
First Nora collects the supplies at West Station Nora collects the supplies at West Station
Second She enters the still-accessible mountain pass The pass collapses; you record it as destroyed
Third She leaves the pass, reaches East Camp, and delivers the supplies You send her along the river route instead
Fourth The mountain pass collapses afterward She reaches East Camp via the river route and delivers the supplies

This table organizes the developments you have chosen to write.

InkWeave does not calculate when the pass will collapse. The causality engine does not find Nora the shortest route.

You decide whether the pass is destroyed.

You also decide whether the river route exists, whether it is usable, and what taking it will cost.

Once those events are confirmed, the causality engine derives the world state from them in order.

In Path A, the mountain pass is still accessible when Nora enters it.

In Path B, its destruction has already happened. The original entry can no longer be used unchanged.

To track whether she travels through the pass, you must also define it as a location and confirm that movement.

Recording only a journey from West Station to East Camp does not tell the causality engine which route she took.

Record the important stages, and her history has something concrete to refer back to.

You can write a later scene first and add its causes afterward

You don’t have to write scenes in event order.

You might begin with Nora arriving at East Camp because you already know how she hands over the supplies and how the people there react.

A few days later, you write her departure from West Station.

Later still, you add the cause of the mountain pass’s destruction.

There is nothing wrong with this approach.

Writing order is the order in which you do the work.

What the story needs to maintain is the order of confirmed events within the manuscript.

Type of order Question it answers Effect on world state
Writing order Which scene did you finish first? Does not directly determine which event happens first
Chapter order in the project Which chapter comes before or after another? Determines the order of recorded events across chapters
Event positions within a chapter Where are acquisitions, movements, and location changes recorded? Determines how the state changes as that chapter progresses
Chapter names and time expressions What is the chapter called, and how does the prose describe time? Do not automatically reorder recorded events

In InkWeave, the causality engine derives state from the chapter order in the project and the positions of recorded events within each chapter.

It does not use the order in which you first wrote the passages.

Nor does a title such as “Chapter 12” make it assume that the chapter must take place before another one.

You can write a later scene first, then add the acquisitions, movements, or location changes it needs at the appropriate earlier positions.

Until those events are in place, relevant checks may identify missing prerequisites.

That can reflect a draft still in progress. It does not mean you have to stop writing.

Flashbacks, recollections, and descriptions of time remain part of your narrative freedom.

At East Camp, Nora can remember crossing the mountain pass three days earlier.

That is a memory. It does not mean she has moved back there now.

The causality engine does not create or reorder events simply because the prose says “three days earlier.”

You decide which world changes need to be tracked and record them at the appropriate positions.

The prose tells the story.

The order of confirmed events provides the basis for deriving its states.

At a different cursor position, the mountain pass has a different state

Organizing a timeline should not mean stopping to search the entire record whenever you write a place name.

InkWeave can bring the world as it was back beside the manuscript.

In Path A, return to a passage before Nora enters the mountain pass.

The scene-aware view can show her location and relevant character information at that moment.

Inspect the mountain pass, and you see the location state at that point in the story.

It has not yet been destroyed.

The Inspector can also show the supplies Nora is carrying then.

When the character and location trigger a movement prompt in the text, you can confirm her entering the pass.

If she is only discussing or remembering it rather than actually arriving, skip the prompt.

Common movements can be recorded through guided choices. You don’t have to prepare a complicated itinerary before writing the next part of her journey.

The location state changes only when you reach the later collapse event.

Return to the earlier crossing scene, and the causality engine still derives the state from that moment. The pass’s eventual destruction does not bring the disaster back into the past.

Path B is different.

When Nora considers the original route, the pass’s destruction is already part of this version’s history.

The scene-aware view and Inspector show the state recorded in this timeline.

If you have supplied images for characters and locations, those images can appear as you work with their names. The location, other characters present, and state information alongside them show what has happened by this point.

To see how Nora eventually reaches East Camp, open her movement history.

Path A preserves her journey through West Station, the mountain pass, and East Camp.

Path B preserves the different route you confirmed there.

You still write her struggle through the rain, her decision to change course, and the moment she finally relaxes after handing over the supplies.

The information stays beside the manuscript.

Check it when needed.

Confirm a movement when it happens.

Otherwise, keep writing.

You don’t have to reconstruct the entire history from memory every time you return to the adventure.

Move the collapse earlier, and the later journey needs another look

You may return to Path A and revise it.

Originally, the mountain pass collapsed after Nora reached East Camp.

Now you want the disaster to happen sooner, so you move the recorded destruction event to a point before she enters the pass.

It looks like a change to one scene’s position.

But Nora’s later movement now faces different conditions.

When the causality engine validates the revised events, it can identify that entering the pass conflicts with the location restriction and show the event that created that restriction.

You can see that a journey which previously worked now needs attention.

You could move the collapse back to its later position.

You could send Nora somewhere else.

Or you could change the extent of the disaster and adjust the location state accordingly.

The choice remains yours.

The causality engine will not calculate an alternative route for her.

It will not pretend the mountain pass is still usable just to preserve the original draft, either.

InkWeave uses its own custom-built causality engine for these checks. It does not hand two scenes to AI and ask whether they seem contradictory.

Event order and explicit rules determine the validation result.

The same starting state and the same ordered sequence of confirmed events produce a deterministic world state.

That verification applies to the world model you have established. It does not include automatic understanding of every meaning in the prose.

When you revise a scene, the corresponding event records therefore need to follow the revision.

If you only change the sentence to say that the pass collapsed earlier, but leave the location change event in its original position, the causality engine will still derive the state from the original record.

Recording the important change lets the display and validation results reflect the world you actually intended to revise.

Each timeline keeps its own event order

You can preserve both journeys.

One lets Nora cross the mountain pass before it collapses.

The other confronts her with an already-destroyed route and sends her into a river journey you had not originally planned.

Even if both end at East Camp, they do not need to become one combined history.

Want to preserve complete versions of both journeys: crossing the pass before its destruction, and finding it already destroyed?

Follow the What If Branching and Multiverse Story Tutorial to save and switch between the projects for each timeline.

This uses the external workflow described in the tutorial. InkWeave does not automatically generate another journey. Completely close InkWeave before carrying out the steps.

The version-saving workflow can be used with the free edition. The causality engine, scene awareness, and advanced features such as automatic causal validation are Pro features.

When you reopen a version, its chapter order, character data, and event records come from that version’s own project.

Path A’s crossing history does not automatically become an answer for Path B.

The river journey added in Path B should not quietly enter Path A’s earlier chapters.

You can compare the two paths, choose one to continue, or preserve both as stories of their own.

What matters is that each timeline can answer from its own event order:

When the character reaches this point, what has already happened?

A timeline gives every step the world it needs

A novel timeline does more than help you remember dates.

It helps you understand why an action was possible when it happened.

Nora can cross the mountain pass not because you remember her eventually reaching East Camp, but because the pass is still accessible before that movement.

She can later deliver the supplies not because they are important in the setting, but because she has acquired them and carried them here along this journey.

The same principle applies to class changes, organizational changes, and story conditions.

A later identity cannot stand in for an earlier one.

Cooperation established later cannot be treated as though it has always existed.

You don’t have to memorize every distinction.

When you return to a passage, the scene-aware view and Inspector can bring back the character locations, items, and relevant states at that point.

Open the history when you need to trace them.

After changing an important event, check whether the later arrangements still hold.

You don’t need to finish an enormous chronology before you can begin writing.

Start with the scene in front of you.

Confirm the important changes.

Let the timeline grow with the adventure.

Reaching the same destination doesn’t mean living through the same events.

In a believable timeline, every step makes sense in the world as it stood then.