A Current Record Cannot Answer the Past
Erin joined a company in January.
She was an HR specialist, belonged to the HR department, and worked in the Taipei office.
The company issued her a laptop identified as A-017 and an access badge for the HR records room. Her direct manager was the HR manager, and she had completed the authorization training required to handle employee data.
In June, she became an executive assistant.
She left the HR department and joined the Executive Office. Her reporting relationship changed with the transfer. She continued using A-017, but her access to the HR records room expired and was replaced by a different set of administrative permissions.
In October, she transferred to the sales department in Kaohsiung.
The company collected A-017 and issued her a new laptop, B-042, along with a company phone. Her workplace, position, department, manager, equipment, and permissions changed again.
The following March, Erin left the company.
She left both the company and the sales department, then returned her laptop, phone, and access badge. The company stopped tracking her location after her departure and no longer treated her as a member of any department.
If someone opened her employee record today, the answer might be simple:
Erin has left the company.
She currently holds no position.
She belongs to no department.
She possesses no company assets.
Every one of those statements is correct.
But if the company needed to investigate who approved a document ten months earlier, the current record would offer almost no help.
Was Erin still an HR specialist at the time, or had she already become an executive assistant?
Which department did she belong to?
Did she have permission to view that document?
Was A-017 still in her possession?
Who was her direct manager?
Was she working in Taipei, or had she already transferred to Kaohsiung?
The problem is not that the company does not know who Erin is now.
The problem is that it needs to know who she was when that event happened.
That is the difference between preserving the latest data and simulating a world.
The Same Person Can Have More Than One Correct Present
Erin does not have four conflicting records.
She simply lived through four different periods.
| Period | Position | Organization | Assets and access | Workplace |
|---|---|---|---|---|
| January to May | HR specialist | HR department | A-017, access badge | Taipei office |
| June to September | Executive assistant | Executive Office | A-017, administrative access | Headquarters |
| October to the following February | Sales specialist | Sales department | B-042, company phone | Kaohsiung office |
| From the following March onward | Former employee | None | None | No longer tracked |
If a system preserves only the final row, it can answer Erin’s current state.
If it preserves every row, it begins to possess a history.
True world simulation must go one step further.
At any point in the event sequence, it must be able to reconstruct the state that was valid there from all changes that had already occurred.
When viewing an event in April, Erin is still an HR specialist.
When viewing an event in July, she has become an executive assistant but still holds A-017.
When viewing an event in November, she has joined the sales department and now holds B-042.
When viewing an event after her departure, she no longer belongs to the company and has returned its equipment.
These answers must not overwrite one another.
Her later resignation cannot erase the fact that she was once an HR specialist.
Her former HR identity cannot continue leaking into the world after she has become an executive assistant.
A person who changes over time should never have one version of the present applied indiscriminately to every moment of their life.
World State Is Not a More Detailed Character Sheet
We could create an extremely detailed record for Erin.
Name.
Position.
Department.
Workplace.
Manager.
Assigned equipment.
Permissions.
Training level.
Current status.
But no matter how many fields it contains, a record that continually replaces old values with new ones still preserves only the latest result.
World simulation takes a different approach.
It does not preserve only what Erin eventually became.
It also preserves the events that made her become that person.
In January, she joined the company and the HR department.
The company issued A-017 and an access badge to her.
She moved to the Taipei office.
A manager-subordinate relationship was established between Erin and the HR manager.
In June, her professional role changed to executive assistant.
She left the HR department and joined the Executive Office.
She lost access to the HR records room and gained administrative permissions.
In October, she left the Executive Office and joined the sales department.
She returned A-017 and received B-042 and a company phone.
Her workplace changed to the Kaohsiung office.
The following March, she left the company and the sales department.
She returned the company equipment she still held.
These are not merely edits made to Erin’s profile.
They are events that occurred in time.
The world knows that Erin was an executive assistant in July not because her current profile says so, but because the event that gave her that role had already happened, while her transfer to sales and departure from the company had not.
World state is not a more complicated character sheet.
It is the combined result of every event that had already occurred at a particular moment.
One Career Change Is Really Several Events
“Erin transferred to the sales department” sounds like one event.
From the world’s perspective, however, it may contain several independent changes.
Her position changed from executive assistant to sales specialist.
She left the Executive Office.
She joined the sales department.
Her direct manager changed.
She moved from headquarters to the Kaohsiung office.
She returned her original laptop.
She received a new laptop and a company phone.
She lost her former administrative permissions.
A new set of skills and attributes became applicable to her sales role.
These changes might happen simultaneously, but they could also be completed over several days.
An employee may receive confirmation of a transfer before moving to the new office.
They may have joined the new department while the equipment replacement is still pending.
They may even have left the company without returning their laptop.
The world therefore cannot see the phrase “department transfer” and silently complete every associated change.
Professional identity, organization membership, relationships, possessions, and location are separate parts of world state.
InkWeave changes them through separate events.
Race and class structures can represent a character’s current identity or role.
Companies and departments can be modeled as factions.
Laptops, phones, and access badges can be modeled as items.
Offices can be modeled as locations.
Managerial, subordinate, and collaborative connections can become character relationships.
Training, permissions, abilities, and other accumulated values can be represented through attributes and flags.
One event does not cause InkWeave to assume that every related event has also happened.
If Erin has left the company but no event records the return of B-042, the world will faithfully show that someone outside the organization still holds a company laptop.
InkWeave will not return the laptop automatically.
In reality, leaving a company does not guarantee that every asset has already been recovered.
The unresolved state might represent an incomplete handover.
Someone may have forgotten to record the return event.
The company may genuinely have allowed Erin to keep the device.
The system cannot decide which explanation is true.
It can only preserve the unresolved state until another confirmed event changes it.
The Cursor Determines the World’s Present
In an ordinary document, the cursor marks where the next character will appear.
In InkWeave, it also identifies how far the world has progressed.
Once characters, items, locations, and events have been established in the manuscript, they remain in the timeline according to the manuscript’s order.
When the cursor rests in the passage where Erin has just joined the company, the causality engine replays only the confirmed events that occur before that position.
At this moment, Erin is an HR specialist.
She belongs to the HR department.
She holds A-017 and an access badge.
She is located in the Taipei office.
The managerial relationship between her and the HR manager is active.
Only after the cursor moves beyond her role change does the world recognize her new professional identity and membership in the Executive Office.
When it moves into her sales period, A-017 has been returned, while B-042 and the company phone have entered her inventory.
After the cursor reaches her departure, Erin still exists as a character in the project.
But she no longer belongs to the company faction, and she no longer possesses those company assets.
The user does not have to create a separate snapshot manually for every passage.
InkWeave replays the world changes that occurred before the cursor, using chapter position and event order.
Later events cannot enter the past prematurely.
Earlier events continue affecting the future until another event changes their results.
The cursor does not carry the latest character sheet into different passages.
Instead, each position asks the same world a new set of questions:
What has already happened here?
What has not happened yet?
Which states are still valid at this moment?
AVG Stage and Inspector Show the Same Moment
As the cursor moves, world state should not remain hidden inside the engine.
The author needs to see it.
InkWeave’s AVG Stage retrieves the world snapshot for the current chapter and event position.
If Erin is the current focus, it can present her identity, status, and location at that moment.
It can also show the other characters and items at the same location, together with the faction, department, and role she held at the time.
When the author returns to a passage in which Erin still belongs to HR, the AVG Stage should not show her later sales role.
When the author moves to a passage after her departure, it should not continue placing her in the HR office.
The Inspector provides a closer view of that same moment.
Where is this character now?
What does she currently possess?
What is her present identity?
Which attributes apply to that identity?
What relationships does she currently have with other characters?
Which factions has she joined, and what position does she hold within them?
The author can also open history views to see when a character moved, when their identity changed, how items entered or left their possession, when relationships were established, and how faction membership changed.
The AVG Stage answers:
What does the world look like at this moment?
The Inspector and history views answer:
Which events produced this state?
They are not two separately maintained sources of data.
They examine the same manuscript timeline and the same state derived from confirmed events.
The interface does not move with the cursor merely to make the screen feel active.
It moves because the world has genuinely reached a different moment.
Returning to the Past Is Not Opening an Old Backup
World state is not the same as document versioning.
A backup preserves what an entire set of data looked like at a particular time.
To inspect four different periods, a backup-based approach might require four character profiles, four organization rosters, and four asset records.
World simulation does not need to duplicate the entire world for every moment.
It preserves an initial state and the changes that actually occurred afterward.
Erin begins as an HR specialist.
A role-change event makes her an executive assistant.
Another identity event later makes her a sales specialist.
Her departure changes her organization state.
A-017 likewise begins as company property.
An assignment event places it in Erin’s possession.
A return event later removes it from her inventory.
At different positions in the world, the causality engine only needs to replay the relevant events in order to derive the correct answer.
This difference becomes especially important when the past is revised.
Suppose the company later discovers that Erin’s appointment as executive assistant did not take effect in June. It officially began in July.
Once the event is moved, the world state for June must be recalculated.
Events that depended on Erin already having administrative permissions may also lose their prerequisites.
The user does not need to locate every independent June snapshot and manually change Erin back into an HR specialist.
Those snapshots were never separate truths.
They were results produced by replaying the same history up to different positions.
Change the cause, and every later result must confront that change.
This Is Not an AI Editor Guessing Her Role from the Prose
When a system can follow the cursor and display a character’s role, possessions, location, and relationships at that moment, many people assume that AI must be reading the passage and guessing what happened.
That is not how InkWeave works.
It does not see “Erin walked into the sales department” and immediately decide that she has transferred there.
She may only be visiting.
She may be remembering the past.
She may be delivering a document for someone else.
She may simply be passing through.
Natural language permits many possible meanings.
If a system silently chooses one, the world state changes because of an unsupported interpretation.
InkWeave takes a more restrained approach.
The user first establishes the important entities in the world.
The user then confirms the events that actually occurred.
Erin’s identity changes only when a role-change event is created.
She joins the sales department only when a faction event establishes that membership.
Her location changes to the Kaohsiung office only when a movement event is confirmed.
A-017 leaves her possession only when its return is recorded.
Once these events enter the manuscript timeline, InkWeave’s self-developed causality engine replays them according to deterministic rules.
Given the same initial state, event contents, event order, and rules, it produces the same result.
Within that explicitly modeled boundary, the result is mathematically guaranteed.
It is not an AI editor reviewing the manuscript.
It does not judge whether Erin’s transfer makes sense.
It does not guess why she left HR.
It does not decide which equipment the company should recover when she resigns.
It calculates and validates only the quantities, sets, identities, locations, ownership, order, and conditions that the user has explicitly modeled.
AI can offer an interpretation of a passage.
InkWeave’s causality engine instead produces a deterministic, reproducible result about the modeled world.
The World Can Only Reconstruct Facts You Explicitly Model
Determinism does not mean omniscience.
If the user never creates B-042 as an item, InkWeave cannot track where it goes.
If Erin’s membership in the sales department is never recorded, the system will not infer it from her job title.
If no managerial relationship is established, the Inspector will not decide that one character manages another simply because their names frequently appear in the same passage.
If company policy requires every departing employee to return their equipment, that requirement must also be modeled explicitly as a condition to verify, or fulfilled through the relevant item-transfer events.
This boundary matters.
World simulation is reliable not because the system pretends to understand everything, but because it knows exactly what it can prove.
Established characters can be tracked.
Confirmed item transfers change possession.
Recorded movement changes location.
Confirmed role changes alter identity.
Faction events change organization structure.
Facts that were never modeled are not invented to complete the picture.
The world model does not pretend to know more than the facts supplied to it.
But it can remain more faithful to those facts than human memory.
If It Can Preserve a Career, It Can Preserve a Fictional Life
Most InkWeave users may never need to manage real company employees.
Erin’s career is not meant to position InkWeave as an HR system.
The example demonstrates something more fundamental:
A person can change identity, organization, location, possessions, relationships, and abilities over time, while the world remains able to recognize who they were at any moment.
Replace the company with a kingdom, and the same structure still holds.
A character begins as a court mage.
They later leave the council of mages and become the king’s secretary.
When war begins, they transfer to a frontline command, gaining new equipment, a new location, and new reporting relationships.
Years later, they leave the kingdom and return the seal of office, while secretly keeping an item they were never meant to take.
Their class can change.
Their faction can change.
Attributes can become applicable or cease to apply as their identity changes.
Relationships can be established, broken, or rearranged.
Items can remain in their possession or be transferred, placed, lost, and recovered.
When the cursor returns to the period in which the character was still a mage, the world does not prematurely treat them as a member of the army.
When the cursor moves beyond their departure from the kingdom, later passages cannot let them continue using privileges reserved for the king’s secretary without a reason.
The career of an ordinary employee may appear mundane.
That is precisely why it reveals whether the simulation truly works.
If a system cannot faithfully preserve when an employee changed roles, which department they joined, or which laptop they possessed, it will have even greater difficulty sustaining belief in a world filled with kingdoms, professions, artifacts, forbidden places, and competing factions.
A fictional world is not exempt from history simply because it does not exist.
The opposite is true.
Readers cannot rely on reality to fill its gaps, so its internal causality must be even stronger.
World simulation does not predict who a character will eventually become.
Nor does it decide what should happen next.
It performs a more foundational task.
Whenever the creator returns to any point in the world, it can faithfully answer:
Who is this person here?
Where are they?
Which organization do they belong to?
What relationships do they have?
What do they possess?
How has the past already changed them?
Data can preserve the latest answer about a person.
World simulation preserves how every answer became the present of its own moment.