How Orbit Uses the Engine During Play

The engine does not require Orbit to read every file before every reply. That would be slow, expensive, and often less accurate. LWE uses routing: load the foundation and current scene, then retrieve specialized guidance and records only when the situation needs them.

The always-relevant layer

During normal play, Orbit should begin from:

• The operating doctrine
• World Clock
• World State
• World Pulse
• Current Location
• Present Characters
• Active Mission, Pressure, and Factions
• Relevant Ruleset and packages

That establishes current truth before narration begins.

GM Instructions are the operating layer

GM Instructions tell the game-running assistant how to use the records during play. They contain the operating doctrine, specialized guides, tool procedures, and compact triggers. They are not setting lore and normally should not be rewritten merely to personalize names or genre vocabulary. Put world-specific truth in the world records; change the GM layer only when you are intentionally changing engine behavior.

Triggered guidance

The package has compact Narrative Triggers that route to larger operating guides when needed. Examples include:

• Character creation
• Combat and danger
• Missions and objectives
• Pressure escalation
• Faction turns
• Travel and exploration
• Time and weather
• Relationships and memory
• Reputation and consequences
• Legacy and successor play
• Rest and downtime

The trigger itself stays short. The detailed guide loads only when the scene calls for it.

The scene ladder

A normal response should internally follow this logic:

1. Establish the current truth.
2. Preserve exactly what the player authored.
3. Separate attempted action from guaranteed effect.
4. Ask what relevant people and systems were already doing.
5. Resolve capability, resistance, cost, timing, and consequence.
6. Narrate proportionally and stop at the next meaningful choice.

This prevents a common failure where a player writes “I pull the hidden weapon I brought and command everyone to obey,” and the world accepts every clause as fact.

The player owns what they attempt and say. The world still decides whether the item exists, whether they possess it, whether anyone obeys, and what consequences follow.

NPCs are allowed to have lives

Orbit may use Character Independent Life and World Pulse’s action queue to determine that an NPC is:

• At work
• Traveling
• Asleep
• Injured
• Frightened
• Busy with someone else
• Following a Faction order
• Refusing
• Already gone

This is not meant to block the player for fun. It keeps the world from rearranging itself solely around the protagonist.

The world can say no

An action may fail without a roll when the fictional barrier is already decisive:

• The character is not present.
• The distance cannot be crossed instantly.
• The item is not owned.
• The information is not known.
• The authority does not exist.
• Another person does not consent.
• An established defense makes the attempt impossible in its current form.

Orbit should state the immediate barrier and return control rather than inventing a meaningless roll.

Ordinary scenes are allowed

Not every locked door hides a conspiracy. Not every tired worker is secretly important. Not every rumor becomes a quest.

The engine intentionally allows quiet scenes, irrelevant details, missed meetings, closed businesses, ordinary weather, and opportunities that expire. This makes actual discoveries and crises feel more believable.

After the scene

Orbit should update only meaningful state:

• Advance the Clock when time passed.
• Update Mission objectives or Pressure escalation.
• Run due Faction or independent-character actions.
• Record important consequences.
• Update Relationships, Memories, or Reputation when behavior changed.
• Update Location Memory or Legacy when the impact is lasting.
• Refresh World Pulse for the next scene.

It should not write a new file after every paragraph.

When Orbit hallucinates

Hallucination often increases when the current state is unclear, conflicting, duplicated, or buried under too much irrelevant text.

Use these fixes:

1. Run Diagnose for broken references or schema disagreement.
2. Confirm World Pulse points to the correct Clock, State, Location, and cast.
3. Resolve duplicate Characters, Locations, or file types.
4. Put shared rules in the Ruleset or Power System instead of repeating them across notes.
5. Use references for important identities.
6. Correct canonical records rather than arguing with the narration alone.
7. Ask Orbit to read the relevant record before continuing a disputed scene.

The engine cannot make a model literally incapable of error. What it does is give the model cleaner truth, stronger routing, and fewer excuses to invent missing connective tissue.