On This Page

They Have Worked Together; That Does Not Mean They Trust Each Other

When investigator Mara first meets the informant Elias, neither trusts the other.

Mara does not know whether Elias is telling the truth.

Elias does not know whether Mara will protect his identity.

After their first meeting, Elias gives Mara the address of a warehouse.

Mara investigates and confirms that the address is correct.

This increases Mara’s trust in Elias.

From Elias’s perspective, however, nothing has changed yet.

Mara has only accepted the information.

She has not demonstrated that she will keep her promise.

A few days later, a hostile organization begins searching for the source of the information.

Mara refuses to reveal Elias and arranges a new hiding place for him.

Only then does Elias begin to trust Mara.

Their trust did not emerge at the same moment or increase at the same rate.

Later, Mara publishes a document Elias asked her to keep secret because doing so is the only way to prevent another disaster.

Mara still trusts the information Elias provides.

Elias, however, believes that Mara has betrayed him.

If their relationship map contains only one line labeled “Mara and Elias: allies,” the most important part of this relationship disappears.

They have worked together.

How they see each other has never been the same answer.

Point in the story How Mara sees Elias How Elias sees Mara
Their first exchange of information Unsure whether his information is reliable Unsure whether she will protect him
The warehouse address is confirmed Begins to trust his information Remains wary
Mara protects his identity Retains the trust already formed Begins to trust her to keep her promise
The confidential document is published early Still trusts his information Believes she has betrayed him

“They Have a Good Relationship” Compresses Too Many Questions

Character profiles often describe relationships with familiar labels: friends, enemies, colleagues, family, lovers, allies, or teacher and student.

These labels are useful. They give an author a quick sense of how two people generally relate to one another.

Once the story begins moving, however, one label soon becomes insufficient.

Two colleagues do not necessarily trust each other.

Family members can still feel hostility.

Two people may be allies only because they currently share an enemy.

A student may respect a teacher’s ability while no longer trusting their character.

A subordinate may obey a manager’s commands while already planning to leave at the first opportunity.

Two characters may love each other deeply while accumulating fear, debt, and resentment that neither knows how to resolve.

“They have a good relationship” compresses many different questions into one sentence:

Who trusts whom more?

Where did that trust come from?

Is either person still guarded?

Do they owe each other anything?

Are they emotionally close, or are they cooperating only because their interests align?

When did these relationships begin?

Which event caused them to change?

If the world preserves only one current label, the relationship loses the process that formed it.

Yesterday, the characters still doubted one another.

Today, an event gives them a reason to cooperate.

Several chapters later, they may behave as though they had trusted each other from the beginning.

The relationship remains.

Its history has been washed away.

A Trusts B Does Not Mean B Trusts A

One of the easiest properties of a relationship to overlook is direction.

Mara trusting the information Elias provides can be represented as:

Mara -> Elias: Trust

Whether Elias trusts Mara is a separate question:

Elias -> Mara: Trust

Both directed relationships may exist.

Only one may exist.

Their values and rates of change do not need to match.

A child depends on a parent, but the parent does not depend on the child in the same way.

An employee may trust a manager’s professional judgment before the manager trusts the employee to work independently.

A character may worship a hero who does not even know they exist.

A victim may fear a pursuer who gives them little personal attention.

Direction changes a relationship from a simple line between two people into a more precise question:

Who feels what toward whom?

That difference can directly affect later events.

Mara may be willing to act on an address supplied by Elias.

Elias may still be unwilling to give Mara more dangerous information.

If the world preserves one shared trust score, a change on one side will be incorrectly applied to the other.

Two people can share the same encounter.

They do not necessarily leave it with the same relationship.

Two Characters Can Trust, Resent, and Owe Each Other at Once

Relationships have types as well as directions.

Mara may trust Elias’s information while disagreeing with his methods.

Elias may remain wary of Mara while owing her his life.

Two people may cooperate because their interests align while privately despising each other.

They may stand on opposite sides of a conflict while still respecting each other’s abilities.

A pair of characters therefore does not need to share only one relationship.

Creators can define the relationship types their worlds genuinely need to track.

For example:

  • Trust
  • Intimacy
  • Hostility
  • Loyalty
  • Fear
  • Respect
  • Debt
  • Suspicion

More types are not automatically better.

If every temporary emotion becomes a numerical relationship, characters quickly turn into unreadable spreadsheets.

The relationships worth tracking are those that continue affecting later events.

Whether Mara trusts Elias may determine whether she acts on his information.

Whether Elias believes he owes Mara may determine whether he accepts another risk on her behalf.

A hostile organization’s suspicion of Mara may determine whether she can enter a location again.

A relationship belongs in the world model not because it can describe every human emotion.

It belongs there because it changes later choices, conditions for cooperation, or the events that remain possible.

Relationships Should Change Through Events, Not Profile Overwrites

Suppose the author sets the default value for trust to zero and records each change in Mara’s trust toward Elias where the information is confirmed.

Confirmed relationship event Change in trust Mara’s accumulated trust in Elias
The first lead is confirmed +25 25
A second lead is confirmed +15 40

Note

The author chooses these values; the software does not assess the characters’ feelings. The default value is only the starting point when a relationship of this type is first recorded. It does not automatically establish a relationship between every pair of characters.

If the author simply edits the trust field on her profile to 40, the latest result is preserved.

But saving only 40 loses when and how that result formed.

Before the first lead was confirmed, Mara had no reason to possess 40 points of trust. Those points did not appear from nowhere; they came from two separate events.

If the author later removes the first lead or rewrites it as false information, they also need to remove or adjust the corresponding relationship event. With only the second increase of 15 remaining, the later trust value becomes 15, not 40.

InkWeave places relationship changes in the manuscript timeline.

Who feels which type of relationship toward whom?

How much does this event increase or decrease it?

Each answer remains at the position where the change actually occurred.

A relationship value is therefore not a current answer repeatedly overwritten by hand.

It is the accumulated result of every confirmed relationship event that came before it.

When the author removes an earlier event, later relationship state is recalculated from the remaining history.

The system does not decide what the characters feel.

But once the creator confirms that an event changed a relationship, that change remains part of the world.

Thresholds Turn Numbers Back Into Understandable Relationship Stages

Seeing a trust value of 40 may not immediately tell the creator what the relationship means.

Does 40 represent practical cooperation?

The beginning of trust?

Enough confidence to entrust someone with a life?

The answer depends on the scale defined by the work.

InkWeave allows creators to define their own relationship types.

Tip

You do not need a complete numerical model of every character’s feelings before you start. Begin with one relationship type that matters to the story, such as trust, and record changes as you write.

Custom setting What it does for relationship tracking
Name Identifies whether a connection tracks trust, hostility, intimacy, or another relationship type
Description Records what this relationship type means in your story
Display color Distinguishes relationship types on the map
Default value Provides the starting value when this relationship type is first recorded
Minimum value Sets the lower bound for the accumulated value
Maximum value Sets the upper bound for the accumulated value
Relationship thresholds Maps value ranges to stage names you define

For example, a creator might define trust on a scale from -100 to 100, with stages such as rejection, wariness, neutrality, trust, and entrustment.

When a relationship value crosses a threshold, the Social Graph can display the corresponding stage name.

The value is no longer only a calculation.

It returns to relationship language that a person can understand.

Different works do not need to use the same scale.

A political story may care most about loyalty, self-interest, and suspicion.

A school story may track intimacy, trust, and rivalry.

A crime investigation may focus on fear, debt, and willingness to cooperate.

A real-world process may need to model only delegated trust, degree of cooperation, or responsibility relationships rather than attempting to quantify complete human emotion.

InkWeave does not define interpersonal relationships for the creator.

It provides a structure through which custom relationships can change over time.

When the Cursor Returns to Their First Meeting, the Graph Should Return to Strangers

By the end of the story, Mara and Elias may have lived through many events together.

They have exchanged information, rescued each other, argued, made promises, and disappointed or betrayed each other’s expectations.

At the end, their relationship map may show several states at once:

Mara still retains some trust in Elias.

Elias’s trust in Mara has fallen back to wariness.

Mara owes Elias an unfulfilled promise.

Elias still acknowledges that Mara once saved his life.

When the author returns to the chapter where they first met, none of these later relationships should travel backward with the cursor.

At that time, they may know only each other’s names.

They may not yet have any formal relationship at all.

InkWeave recalculates relationship state according to the current position in the manuscript.

Cursor position in the story Mara’s trust in Elias Elias’s trust in Mara
Before their first meeting No relevant relationship event recorded yet No relevant relationship event recorded yet
After the first lead is confirmed Includes the recorded increase from the information No change recorded in the reverse direction yet
After Mara protects his identity Retains the trust accumulated so far Includes the recorded increase from her protection
After the document is published early Does not automatically decrease because of her own action Includes the decrease confirmed by the author

The Causality Engine calculates only confirmed relationship events before the cursor position. Even within the same chapter, stopping before or after an event can give you a different answer.

The same pair of characters does not need to share the relationship they have at the end of the story in every earlier chapter.

Every point in time has its own relationship state.

Social Graph Shows the Relationship Now, Not at the End of the Story

A static relationship map is useful for introducing a cast: who belongs to the same family, who works on the same team, who is an enemy, and who may eventually become a lover.

But if the relationship map always displays the final version, it can reveal later developments too early. It can also show an author answers that do not belong to the passage they are revising.

InkWeave’s Social Graph does not read only fixed connections from character profiles.

It calculates the relationships that have already formed at the current chapter and cursor position.

With Mara at the center, the graph can show:

Information on the map What the author can check
Connected characters Whom she has a recorded relationship with at this point in the story
Connection direction Whether the relationship runs from her to the other character or the other way around
Relationship type and color Whether the connection represents trust, hostility, or another custom relationship type
Accumulated value How far the confirmed events so far have changed the relationship
Threshold stage Which author-defined relationship stage the current value falls into

Different relationship types can use different colors.

If the same pair has several relationships, they do not need to be compressed into one label.

As the cursor moves forward or backward, the Social Graph updates with the current world.

The graph is not merely a summary assembled after the story has been completed.

It is the network of relationships that exists at any point the creator chooses to inspect.

Relationship History Explains Not Only the Current Value, but Why It Got There

Knowing that Elias currently has a trust value of negative 35 toward Mara is only a result.

The creator may still need to ask:

Where did this relationship begin?

Which event increased the trust?

Which promise was left unfulfilled?

In which chapter did the relationship cross a threshold?

Did one major betrayal create the current wariness, or did many smaller events accumulate over time?

InkWeave can display a character’s relationship changes with everyone else.

The creator can also select another character and inspect only the relationship events between that pair.

History is ordered by chapter and event position.

Every change preserves the relationship type, the amount of change, and the accumulated result at that moment.

Clicking a relationship history entry takes you back to its event position in the corresponding chapter, where you can reread the scene that changed the relationship.

The history helps you locate the source of a change. Understanding why a character trusts, doubts, or betrays someone still means returning to the manuscript.

This gives the same numerical value its context back.

Two relationships can both contain 40 points of trust and still have entirely different histories.

One may come from years of cooperation; another from a single extraordinary rescue.

One may have risen steadily. The other may once have reached complete confidence before betrayal reduced it to its current value.

The same number does not mean the same history.

How a character responds next often depends on that history.

When Two Names Meet, the World Can Ask Whether the Characters Did

Two character names often appear in the same paragraph of a long manuscript.

That does not necessarily mean the characters are meeting.

Mara may read Elias’s name in a report.

Elias may hear about Mara’s actions from someone else.

The author may compare their choices in the same passage.

InkWeave therefore does not establish a relationship automatically when two character names appear near each other.

The scene view beside the manuscript first checks the current world-state snapshot.

Do the characters already have a relationship?

Does the relationship point in only one direction?

Are they currently in the same location?

If no relationship has been established, or only a one-way relationship exists, the world can raise the question.

If the characters are in different locations, it can remind the creator to confirm whether an in-person interaction is actually occurring.

The creator can establish a general relationship.

They can open detailed settings and select a relationship type and amount of change.

They can add a character movement.

They can also skip the interaction entirely.

You can respond to these prompts when needed or simply keep writing. You do not have to record a relationship change every time two character names appear near each other.

The passage may describe discussion, memory, comparison, or remote communication. The world does not need to change.

The proximity of two names is only a signal.

Whether the characters met, whether a relationship was established, and how much the encounter changed remain decisions for the creator.

This Is Not AI Analyzing Emotion

The manuscript might say:

Elias remained silent for a moment, then opened the door anyway.

InkWeave does not use AI to decide whether the silence expresses trust, fear, guilt, or the absence of any other choice.

It does not decide on the creator’s behalf that:

Elias’s trust in Mara increases by 20.

His hostility decreases by 10.

His intimacy increases by 5.

Emotion in natural language is too complex.

The same action can arise from entirely different reasons.

A character may even perform an emotion opposite to what they truly feel.

InkWeave does not pretend that it can understand a character completely from one sentence.

The creator first decides which relationship dimensions are worth tracking.

They then confirm whether an event actually changes one of those relationships, in which direction, and by how much.

InkWeave’s self-developed causality engine performs a different task:

It deterministically calculates the current result from the source character, target character, relationship type, amount of change, and event order.

The same events and settings produce the same relationship state.

If an earlier event is removed or revised, the later relationship graph is recalculated from the new history.

Relationship values obey the minimum and maximum bounds defined by the creator.

Thresholds translate those calculated values into the work’s own relationship stages.

The mathematical guarantee applies to explicitly recorded direction, type, accumulation, boundaries, and order.

It does not claim to prove what a character feels.

InkWeave is not an AI editor auditing emotions.

It does not let a model decide whom a character should love, trust, or betray.

Numbers Do Not Replace Character Performance

The ability to track a relationship does not mean a character should be reduced to a handful of numbers.

A trust value of 40 cannot write a convincing conversation.

A hostility value of 70 cannot decide whether a character draws a weapon, flees, negotiates, or pretends to cooperate.

Different characters can make entirely different choices within the same relationship stage.

One person remains polite while wary.

Another hides secrets even when they trust someone.

Someone may love another person deeply and still betray them because of a conflict in values or allegiance.

Relationship state provides background conditions.

How a character performs those conditions remains part of the creative work.

The same is true in reality.

Whether a manager trusts an employee to handle a task independently and whether the employee trusts the manager to accept responsibility are already two different directions.

InkWeave is not an HR system, customer relationship management platform, or psychological assessment tool.

A numerical value should never be presented as the complete emotional truth of a real person.

InkWeave can simulate relationship dimensions the creator explicitly defines because they affect later events.

The ability to express these real asymmetric structures also means fictional worlds no longer need to reduce every character connection to an unchanging label such as “friend” or “enemy.”

Believable Relationships Are Not Always Harmonious; Every Change Has a Source

Characters do not need to maintain the same attitude forever.

They can change their minds.

Misunderstand each other.

Draw different conclusions from the same event.

They can trust someone while still refusing to forgive them.

What damages the credibility of a relationship is often not that it changes.

It is that the relationship becomes something else without anything causing the change.

Yesterday, the characters still distrusted each other.

Today, they entrust each other with their lives without reservation.

A betrayal has already occurred.

Later conversations proceed as though trust was never damaged.

One character stopped believing another long ago.

The relationship map still labels them simply as allies.

When relationships remain static reference data, every new event makes that data more likely to fall behind the history the characters have actually lived.

InkWeave preserves every relationship change the creator confirms at the position where it occurs.

Trust has direction.

The same pair can carry several relationship types.

When the cursor returns to the past, the characters return to the relationships they truly had then.

A believable character relationship map does more than connect every person.

It lets every connection remember:

When it appeared.

Which events it passed through.

Why it became what it is now.