What if she kept the badge?
The city gates will close before dawn.
Mara stands at the North Gate checkpoint. She is a captain in the city guard, carrying a badge that lets her pass through military checkpoints inside the city.
Facing her is Xien, a friend she has known for years.
He is suspected of leaking intelligence to the enemy. The city guard has orders not to let him enter.
Xien says someone inside the city can prove his innocence. If Mara lends him the badge, he has a chance to find that person before the city is sealed off.
In the original story, Mara hands it over.
She chooses to trust her friend.
But as you write the scene, another possibility occurs to you:
What if she refuses?
She might keep her position. Xien might leave. The person who could have cleared his name might never get the chance to tell the truth.
This is where a What If story begins.
You don’t need another ending planned in advance. At one important moment, a character makes a different choice. Then you follow that path as far as you want to take it.
Changing the conversation is easy. Keeping its consequences alive throughout the rest of the story takes more care.
Who has the badge afterward?
Is Mara still a captain?
Where does Xien go?
When they meet again, can they still work together?
If you have to remember every answer yourself, exploring another future can quickly become another set of records to maintain.
But writing can feel different.
You keep writing. Beside the manuscript, the world gradually takes on a new shape, carrying the changes you have already confirmed.
Start with the scene in front of you in InkWeave
You don’t have to build an entire alternate universe before you begin.
Nor do you have to fill in every character’s biography, every relationship, and every future development.
This scene needs Mara, Xien, and the badge. Start by creating those two characters and that item, with Mara as its initial holder.
When you need to track who is at the North Gate, add it as a location.
When Mara’s position becomes important to later events, create the city guard and its membership relationships.
The world can grow with the manuscript.
Once these names are linked to the characters, items, and locations you have created, writing them is no longer just a matter of putting the same words on the page again.
InkWeave’s scene-aware view follows the entities you are working with and your position in the story, displaying relevant information.
As you write about Mara, you can see where she is at that point and who is there with her.
When you focus on the North Gate, you can check which characters are present and which items have been left there.
For the badge, the Inspector shows who holds it and its transfer history.
For the city guard, you can see its membership and structure at that point in the story, rather than consulting an organization chart that always shows the latest version.
| What you encounter while writing | Information brought into view | What you do |
|---|---|---|
| Mara | Her location, status, and organizational affiliation at that point | Check when needed, then continue writing her actions |
| The North Gate | The characters present and items left there | Confirm what is actually in the scene |
| The pass badge | Its holder and transfer history | When a transfer happens, confirm who receives it |
| The city guard | Its members, leader, and reporting structure at that point | Record a change when the organization actually changes |
If you have added images for characters, items, or locations, the scene-aware view can bring those images into view too.
A character is more than a name on a reference page. They appear alongside their location, the other characters present, and their organizational affiliation at that moment.
When you want more detail, open the Inspector to check an item’s history, character relationships, or an organization chart. Otherwise, stay with the sentence you are writing.
This feedback doesn’t require you to keep stopping to fill out forms. Relevant information sits beside the manuscript, so you don’t have to leave the scene every time you need to look something up.
When a character and an item trigger an interaction prompt in the text, InkWeave can show the transfer direction for you to confirm.
If Mara really hands the badge to Xien here, choose that transfer.
If they are only discussing it, skip the prompt.
Common actions such as moving, acquiring an item, and transferring it can be recorded through direct choices. Open the detailed settings when the scene needs more.
You confirm what happened.
The causality engine keeps those confirmed changes in the world’s history.
You are still putting the adventure in your head into words. But you can also see, on screen, how that adventure is changing the world.
One starting point, two paths
Before the choice divides the story, both versions share the same starting state.
Mara holds the badge.
Both characters are at the North Gate checkpoint.
Mara is still a captain in the city guard.
Xien has not entered the city.
Their relationship has not yet changed because of his request.
From here, you write the two paths separately.
Path A: Mara hands over the badge.
Xien passes the checkpoint and reaches the inn inside the city where he has arranged to meet.
Mara stays at the North Gate.
At the change of shift, she admits that she disobeyed orders and let him through.
You write the city guard removing her from her post as captain and from the organization itself.
A few days later, she meets Xien again. They agree to find the person who can prove his innocence together.
Path B: Mara refuses to hand over the badge.
Xien does not pass the checkpoint.
He leaves the North Gate and heads to an old waystation outside the city.
Mara remains in the city guard.
But in this version, you write the argument as a break in their friendship. Xien no longer wants to share his plans with her, and they stop working together.
| What changes | Path A: She hands over the badge | Path B: She refuses |
|---|---|---|
| Who holds the badge | Xien | Mara |
| Where Xien goes afterward | An inn inside the city | An old waystation outside the city |
| Mara’s position and membership | Later removed from her post and from the city guard | Keeps her position and membership |
| Their relationship | Later events confirm continued cooperation | A later rupture ends their cooperation |
InkWeave does not automatically arrange these futures because Mara gives away the badge or refuses to do so.
Handing over the badge establishes only the item transfer.
Her dismissal, departure from the organization, later meeting, and relationship change are separate events that you write and confirm.
Refusing a request does not necessarily end a friendship, either. You could write Xien understanding her predicament and looking for another way in.
That freedom is the point of What If writing.
You can take the different choice toward any future worth exploring.
Once you confirm those changes, the scene-aware view and Inspector can display the new character, item, and organization states derived from that version’s history.
In Path A, Mara no longer appears with her former organizational credentials.
In Path B, the badge is still in her possession.
The differences between these futures no longer have to live only in your memory.
The next time she needs the badge, the choice matters
A few days later, Mara learns that an important record is hidden in the armory.
She needs to get inside.
You establish the normal entry requirements for this location: anyone entering must hold the pass badge and still be a member of the city guard.
Both versions can reach the same armory.
But the Mara standing at its door does not have the same options in both.
| What matters at the armory | Path A | Path B |
|---|---|---|
| Does Mara hold the badge? | No. Xien still has it. | Yes. |
| Is Mara still a city guard member? | No. She has been removed. | Yes. |
| Can she use the original entry method? | Not as things stand. | Yes. |
| Is Xien willing to help? | Yes. | Not at present. |
In Path A, as you write about Mara and the badge, you can see the item’s current state.
She has already handed it over.
Check the city guard, and she is no longer a member.
This information doesn’t decide your next sentence. It lets you see the consequences of your earlier writing while you are working on the current scene.
Mara could ask Xien to return the badge.
But recovering the item would not also restore her membership.
She could seek help from someone inside, obtain new permission, or risk another entrance. Each approach can lead to new scenes.
In Path B, she still meets the normal entry requirements.
Yet if she needs Xien’s background knowledge to understand the record, she faces a different obstacle.
She has kept her way in but lost his cooperation.
The same armory can therefore support two different adventures.
The point is not to score the choices as better or worse. It is to let the characters enter the next scene with their own histories intact.
Explore another version without losing your original draft
Wanting to explore Path B doesn’t mean deleting Path A.
You can preserve the complete project from before the choice, then follow the version-saving workflow to continue the two stories separately.
What you preserve is more than different dialogue.
It includes the chapters, characters, items, locations, organizations, and confirmed events belonging to each version.
Path A keeps the history in which Xien receives the badge and Mara leaves the city guard.
Path B keeps the history in which Mara still holds the badge and the two friends later stop cooperating.
When you reopen a version, InkWeave reads that version’s own project data.
The two manuscripts do not have to share one conflicting set of latest reference information.
For the steps to create and switch between story versions, see How to Use InkWeave to Write What If Branches and Multiverse Stories.
This requires the external workflow described in the tutorial. It is not a built-in InkWeave button that generates another future. Before saving or switching versions, completely close InkWeave so that autosave does not carry content into the wrong version.
The version-saving workflow in the tutorial can be used with the free edition. The causality engine, scene awareness, and automatic causal validation described in this article are Pro features.
The tutorial covers the practical steps.
Once you return to the manuscript, your work is still to write the story that follows the choice.
You don’t have to study the causality engine before you can write
After confirming a transfer, you don’t need to edit two separate character inventories and write a transfer summary just to bring the dynamic state into agreement.
The causality engine derives the relevant character and item states from the recorded events.
Move the cursor to a point before the transfer, and Mara still holds the badge.
Move past it, and the world shows Xien as its holder.
Before Mara’s dismissal, her organizational relationships remain as they were then.
Afterward, the world reflects the changes that followed.
The scene-aware view and Inspector bring these answers back to the writing space.
You don’t need to learn the underlying data structures or calculations to use them.
InkWeave runs this world simulation on its own custom-built causality engine. It does not ask AI to read the surrounding prose and guess the world’s state.
Instead, the causality engine replays the events you have confirmed through explicit state transitions and condition checks. The same starting state and event sequence produce the same resulting state.
That certainty comes from the world model you have established.
It does not mean the causality engine understands every literary meaning, or knows what you have planned but never recorded.
Suppose you later write Mara transferring the badge again in Path A without first getting it back. The causality engine can identify the missing possession requirement for that transfer.
You can return to the relevant point and add an event in which she recovers it.
Or you can rewrite the later scene.
If you also want to validate the armory’s entry rules, explicitly define the important qualifications as story conditions so that later events can check them.
You don’t need a condition for every line of dialogue, expression, or hesitation.
Start with the characters, items, and events the scene needs. Add more detailed rules when the story calls for them.
When you revise earlier events, later states and check results update as validation runs again. The project-wide dashboard can gather the affected issues, helping you return to the relevant events and review them.
The causality engine handles the underlying calculations.
In front of you are the sentence you are writing, the world at that point in the story, and reminders you can respond to when needed.
An alternate future should be a world you can keep writing in
After a few chapters, you might prefer Path A.
Mara loses her position but joins Xien on a journey you had never planned.
Or you might prefer Path B.
She keeps her place in the city guard but has to investigate the truth without her friend’s help.
Both paths can continue.
You can also choose one and leave the other where it is for now.
An experimental version doesn’t have to remain secondary just because it began as an experiment. If another choice leads to a stronger story, that version can become the one you want to finish.
What If writing doesn’t ask you to write every possible future.
It gives you room to explore a moment that once had only one answer.
And in InkWeave, exploring that future doesn’t have to feel like facing a blank page alone.
As you write about Mara, you can see her location and role at that moment.
Return to the North Gate, and you can check who and what are still there.
When you need the badge, you can trace whose hands it has passed through.
Look at the city guard again, and you can see whether earlier events have changed its structure.
The information stays beside the manuscript.
Confirm a change when one happens.
Skip the prompt when something is only mentioned.
Open the history when you need to trace it back.
You still decide where the characters go. InkWeave faithfully brings the adventure you have written and confirmed into view.
Another choice becomes more than an alternative passage.
It gains its own characters, possessions, relationships, and past.
You don’t have to build an entire alternate universe first.
Start with one different choice.
Then keep writing, with that world beside you, and see what future grows from it.