What Links to What—and Where Truth Belongs

References are how LWE becomes a connected engine instead of a collection of isolated pages. The trick is meaningful linking, not maximum linking.

A reference should answer a useful question. “Which Location is this Character currently in?” is useful. “Can I attach every Lore file to every Character who may have heard of it?” usually is not.

The ownership rule

Each kind of truth should have one canonical owner. Other files reference it instead of copying it.

When two records disagree, resolve the conflict in the canonical owner first.

Foundation links

A healthy foundation usually has these connections:

• Setup Profile tracks which foundation systems are enabled and configured, stores creator decisions, and may hold project defaults such as the World Lexicon.
• World Clock references its Calendar and current Location.
• World State references active Pressures, recent Events, active Lexicons, and major Factions when useful.
• World Pulse references the active Clock, State, Location, player Characters, present Characters, active Mission, Pressures, Factions, and scene Lexicons.
• Characters reference their Ruleset, packages, current Location, learned abilities, techniques, equipment, relationships, and current Pressure when relevant.

Setup should establish these foundation links. You should not have to manually connect every one from scratch after a normal installation.

Story links

Use source links to preserve causality:

• A Mission may reference the Pressure or Faction that created it.
• An Event may reference participants, Location, Factions, and consequence rows.
• A Collateral Incident may reference who caused it and where it happened.
• Reputation references the subject and affected Factions or audiences.
• A Legacy may reference its originator, origin Event, affected Factions, and affected Locations.
• A pending consequence in World Pulse may reference its source Event, Mission, Pressure, and target.

These links let Orbit trace why something is happening instead of inventing a new explanation later.

Relationship and memory links

• Relationship Profile references Character A and Character B.
• Specialized bonds reference the same Characters and, when one exists, the canonical Relationship Profile.
• NPC Memory references the remembering NPC, related Event, involved Characters, and people the memory was shared with.
• Location Memory references the Location and source Events.

Do not copy the full Relationship state into every Memory. Do not copy every Memory into both Character descriptions. Use references and short summaries.

Linking versus naming

Writing “the Crimson Court” in a notes field is readable text. Referencing the Crimson Court Faction creates a stable structural connection.

Use a reference when the engine needs to:

• Navigate to the record
• Filter choices
• Compute counts or status
• Preserve identity through renaming
• Trace cause and effect
• Update connected systems

Use plain text when the name is only part of a sentence and no structural behavior depends on it.

Avoid circular clutter

Some circularity is natural—Characters belong to Factions, and Factions have members. But do not maintain two manual lists unless both are intentionally useful. Choose a primary direction and let the other remain a convenience when needed.

Similarly, World State may list active Pressures, but each Pressure remains the owner of its escalation. World Pulse may surface a due consequence, but its source Event remains the owner of what originally happened.

The “why is this linked?” test

Before adding a reference, finish this sentence:

This link exists so the engine can…

If the answer is only “because the field was there,” leave it blank.

A clean graph of meaningful references is more powerful than a dense web nobody can explain.