The coup is over. Now the histories begin to diverge.
Princess Ilea stands outside the palace gates.
Regent Lod still controls the royal court. Guard commander Saen has promised to support her, while his adjutant, Mien, waits with the soldiers for orders.
You have prepared a coup.
In one version, Ilea enters the palace and takes power from Lod.
In the other, word leaks too soon. Lod holds his position, and Ilea and Saen are expelled from the court.
At this point, the two timelines are clearly different.
But if the difference ends with the coup itself, while everyone afterward keeps talking, commanding troops, and entering the armory as before, the struggle has done little more than change the name on the throne.
The real difference may surface several chapters later.
A crisis breaks out at the border. Saen needs to mobilize the guard.
In the successful version, he may deliver orders on Ilea’s behalf.
In the failed version, he is the same man, carrying the same badge, facing soldiers who know him. Yet they may no longer recognize his authority to command them.
He may even need help from his former adjutant.
When you write alternate history fiction, changing the outcome of a major event is only the beginning. You also need to ask:
Who now answers to whom?
Who has lost their former position?
Who still holds a resource but no longer has permission to use it?
These are the changes that give another history somewhere to grow.
A new leader doesn’t automatically make everyone change sides
Put the kingdom’s two possible futures side by side.
Before the coup, Lod leads the royal court. Ilea and Saen are members, and Mien reports to Saen.
You decide to continue both versions:
| What carries forward | The coup succeeds | The coup fails |
|---|---|---|
| Leader of the royal court | You confirm Ilea as the new leader | Lod remains in power |
| Lod’s position | You separately record his departure from the court | He retains the leadership |
| Saen’s reporting relationship | You make Ilea his direct superior | You record his departure from the court |
| Mien’s place in the organization | He remains under Saen | He stays in the court; you assign a new superior later |
| Armory authorization | You confirm that Saen’s permission remains valid | You separately revoke his permission |
| Border crisis | Saen may mobilize the guard for the new court | He may need Mien’s help to reach the troops he once commanded |
These are not political outcomes predicted by the causality engine.
They are histories you have chosen for the two timelines.
Ilea taking power does not necessarily mean Lod leaves the organization. You could keep him as an adviser or give him another role.
Saen’s departure does not necessarily mean Mien follows him. Mien could stay, be reassigned, or choose to leave later.
Changing a leader, joining or leaving an organization, changing a title, and adjusting reporting relationships are separate changes.
Loyalty, fear, and political beliefs are another matter again. A new leader’s name cannot rewrite them all.
You might have Mien obey Lod in public while quietly helping Saen. Or he might sincerely believe the coup should never have succeeded.
A person’s place in an organization does not always match their private choices.
That distinction is what keeps political fiction from reducing everyone to one of two opposing camps.
Start with this transfer of power, not the entire kingdom
You do not need every noble family tree, provincial official, and military roster before you can write this coup.
In InkWeave, you can start with the royal court and the few characters who actually appear in the scene.
When Mien’s choices become important, add his reporting relationship with Saen.
When the story reaches the armory, add the location, the badge, and the authorization condition you need to track.
The world can take shape as you write.
Factions do not have to mean enemies and allies, either. A royal court, army, merchant guild, family, or religious order can all be organizations whose membership and structure matter to the story.
By selecting the relevant character and faction, you can record a leadership change, a member’s arrival or departure, a new title, or a reporting relationship at the point where it happens in the manuscript.
Not every passage about politics needs an event.
Ilea standing outside the palace and declaring her right to rule is a declaration. Confirming her as the court’s leader is a change in organizational state.
Saen suspecting that Mien will betray him is a thought. Confirming that Mien now reports directly to Lod is a reporting change you can track.
Keeping these things separate does not make writing more restrictive.
It lets you record only the conditions the later story needs, while leaving the rest free to unfold in the prose.
The organization chart should reflect the scene you’re writing
After writing the successful coup, you might return to an earlier chapter to add the scene where Saen first accepts orders from Lod.
You need the royal court as it was then.
Not the latest organization chart, with Ilea already in power.
InkWeave’s Inspector lets you view the faction structure at the cursor’s position in the story. It also provides a chart of the story’s final recorded state, so you can distinguish this moment from what happens later.
Before the coup, Lod is still the leader. Saen reports to him, and Mien reports to Saen.
Only after the confirmed transfer of power in the successful timeline does the chart show Ilea in charge and the structure you have arranged around her.
In the failed timeline, the court takes its shape from a different sequence of events. Saen may no longer be on the membership list. Mien remains, but his direct superior has changed.
This is useful while writing, not just while looking things up.
As you write Mien receiving an order, Saen returning to the palace, or Ilea gathering members for the first time as their leader, the scene-aware view and Inspector beside the manuscript can show the relevant characters and faction as they stand at that moment.
Information appears when you need it. Events still require your confirmation.
Mentioning an organization does not make InkWeave ask you to arrange a new action for everyone in it. The faction can simply show its leader, members, and structure while you continue writing the conversation.
If you want to know why Mien has a different superior, you can consult the faction’s events or his faction history and return to the change that caused it.
The organization chart is no longer just an appendix you update after writing the plot.
It brings the power changes you have already written back into view. You can write the adventure while seeing where its people stand.
The same badge can mean different things in different timelines
When Saen leaves the court, you might let him keep his guard badge.
That makes sense.
An item not being confiscated does not mean its owner’s permission remains valid.
Several chapters later, Saen arrives at the armory. The guard recognizes both the badge and the man.
But in the failed version, the answer might be:
“I know who you are. That’s exactly why I can’t let you in.”
Tracking who holds the badge is not enough to answer this scene.
Possession and authorization are different world conditions.
| What still looks the same | What needs to be checked |
|---|---|
| Saen still carries the guard badge | Is his permission to enter still valid? |
| Mien is still called an adjutant | Who does he report to, and whose orders does he follow now? |
| The court occupies the same palace | Have its leader and membership structure changed? |
| Saen still knows the guard | Does he retain command authority, or does he need someone else’s help? |
| Ilea is still a princess | Has she actually taken power in this timeline? |
InkWeave can track the badge’s holder.
It does not infer everything the badge means in every political situation.
If access to the armory matters later, you can explicitly define a boolean flag: “Saen’s armory authorization is valid.”
In the successful timeline, you keep that authorization valid.
In the failed timeline, you record it as no longer valid at the scene where it is revoked.
When a later scene depends on Saen entering through the usual authorized route, you can place a condition check there to verify that his permission is valid at that point.
The causality engine checks the condition you have explicitly recorded.
It does not treat the badge in his hand as proof that permission still exists.
Losing authorization does not stop the story.
Saen can ask Mien for help, negotiate, sneak in, or abandon the armory and find resources elsewhere.
Those are new choices.
His old permission should not quietly return just because you need the next battle to go ahead.
One person’s departure doesn’t have to take everyone with them
After the failed coup, you record Saen’s departure from the court.
What happens to Mien?
The question concerns both his feelings and the organization’s structure.
InkWeave’s faction departure options let you choose how to handle the departing member’s subordinates.
| Departure handling you choose | Result in this example | Story possibilities |
|---|---|---|
| Subordinates leave with him | Mien leaves the court with Saen | They lose their former positions and seek new support together |
| Direct subordinates move to his former superior | Mien now reports to Lod, Saen’s former superior | He must answer directly to the ruler they tried to overthrow |
| Subordinates stay without a direct superior for now | Mien remains in the court, awaiting reassignment | The gap can invite rivalry, persuasion, and new choices |
The causality engine is not deciding whom Mien should be loyal to.
You choose how the organization handles the departure. The engine derives the result from the membership and reporting relationships at that point.
If you keep Mien in the court without assigning a new superior, that gap can be shown for you to review.
It may be intentional.
Mien not knowing whom to report to tomorrow could be the next scene.
If you later decide that he should report to Lod, record that new relationship. Whether Mien accepts the arrangement or secretly resists it still belongs in the story.
An organization chart becomes more than a set of attractive connecting lines.
Changing one line can mean that tomorrow, someone has to knock on a different door and explain their choices to a different person.
The causality engine records power changes; it doesn’t predict politics
InkWeave uses its own custom-built causality engine.
It does not send your coup scene to AI and ask who should succeed the ruler, which soldiers will defect, or how long the kingdom will survive.
You establish the characters, factions, and initial data, then record confirmed changes in the manuscript’s event sequence.
Following the chapter and event order, the causality engine derives the members, leader, titles, and reporting relationships at each point.
The same initial state, rules, and event sequence produce the same derived result.
That mathematical guarantee applies within the model you have explicitly defined.
It is not a prediction of human nature, politics, or the course of history.
Within the faction model, the causality engine can check for a leadership vacancy after a leader leaves, gaps in reporting relationships after a member’s departure, and whether the organizational structure remains consistent.
When your chosen departure handling affects subordinates, it can show the people actually affected rather than merely removing the departing character from the screen.
If you later revise an earlier chapter and give Saen another subordinate, the departure’s previously confirmed effects may change and need another review.
But the causality engine will not decide whether:
- The new leader wins public support.
- Mien seeks revenge.
- The border war ends in victory.
- Ilea’s rule lasts for years.
Those still require your observation, choices, and storytelling.
InkWeave helps preserve the facts you have chosen, so the later story does not accidentally replace them with a different history.
Keep both histories, then decide which one to continue
The successful and failed coups do not have to stay crammed into one set of worldbuilding notes, with reminders saying “check which version this belongs to.”
You can preserve two complete story versions.
The successful timeline keeps the chapters, characters, organizational structure, and events that follow Ilea’s rise to power.
The failed timeline keeps Lod in power, Saen’s departure, and Mien’s history as he finds a new place in the court.
Want the successful and failed coups to become separate worlds you can keep writing?
Follow the What If Branching and Multiverse Story Tutorial to save and switch between complete story versions, then continue writing within each timeline.
This workflow uses an external versioning tool. It is not a built-in InkWeave button that generates another history.
Before saving or switching versions through that workflow, completely close InkWeave and follow the tutorial. This prevents autosave from writing content into the wrong version.
The external version-saving workflow works with the free edition. The scene awareness, causal state derivation, and automatic validation described in this article are InkWeave Pro features.
When you reopen a version, the causality engine uses the events actually saved in that timeline.
The failed timeline cannot borrow Saen’s authorization from the successful one.
The successful timeline cannot reuse the exile already written in the failed version unless you separately make it happen there.
You can revise either version.
But each revision needs a place in that version’s own history.
When power changes hands, “we” can change too
Before the coup, Saen and Mien may mean the same people when they say “our guard.”
After the failed coup, the same words may mean different things.
Saen remembers the troops he once commanded.
Mien faces the people who still need orders, supplies, and someone to hold the gates tomorrow.
They can still trust each other. They can occupy different positions without either betraying the other.
You do not need to show readers an organization chart on every page.
What they need to see is how people address one another, whose orders are followed, who refuses, who helps, and how those changes affect their choices.
But when you can see the structure at that moment, you have less to hold in your head while writing dialogue: when each person left, who took over, and whose authority ended.
InkWeave can show those confirmed changes beside the manuscript as you move through the story.
Write about the royal court, and you can see who holds power then.
Write about Saen, and you can check whether he still belongs to it.
Return to a chapter before the coup, and later power relationships do not have to overwrite the past.
A convincing alternate history does more than give a major event a different outcome.
It lets people live in the world that outcome created.
When the throne changes hands, changing a name isn’t enough.
The story needs to remember who, from that moment onward, must answer to someone else.