Grow the World Without Breaking It

Setup is the beginning, not the end.

Once the playable spine works, you should be able to add a city, faction, species, dungeon, academy, religion, political system, or entire region without becoming an LWE maintainer.

Use these recipes as the default way to think.

“I want to add an important NPC”

Create a Character.

Give them identity, role, ordinary life, capabilities, obligations, knowledge, and the relationships that already matter.

If absence matters, add routine anchors.

If repeated interaction begins to matter, add Living Memory and a Relationship Profile.

If their cognition becomes independently important, consider an Inner World Profile.

Do not start at Deep tier because you hope the player will like them.

Let importance be earned.

“I want to add a city or region”

Create the Location hierarchy and connect it to the existing map.

For important inhabited places, add:

• routes
• population cohorts
• services
• local authority
• temporal rhythms if time matters
• resources or dependencies that can affect play
• one-hop propagation carriers only where real

Then create the Factions, Pressures, Characters, and current state that make the place active.

A Location folder full of beautiful descriptions is not yet a living region.

“I want a faction to move offscreen”

Create or strengthen a Faction with:

• goals
• current operation
• capacity
• dependencies
• reach or territory
• allies and rivals
• what it knows
• what could block it

Then give it a reason to wake: time threshold, Signal, Pressure, resource change, political development, or similar cause.

Do not schedule meaningless “faction turns” just so every group does something.

Quiet is valid.

“I want a problem that gets worse if ignored”

Use Pressure.

A Pressure is not automatically a quest.

Define what is currently true, what drives escalation, what thresholds matter, what consequences can occur, and what could reduce or transform it.

If somebody offers the player a concrete objective in response, that may become a Mission.

“I want a quest”

Use Mission when there is a real objective.

Define:

• what is known
• what is actually required
• stakes
• urgency if any
• complications
• hidden truth where appropriate
• outcomes

A Mission can be declined.

Declining it should not resurrect the same offer forever because the pacing system wants content.

“I want shops, hospitals, schools, transit, or services to behave realistically”

Start with the Location service/affordance.

Connect it to the Faction that runs it and Resource dependencies if those matter.

Add operating rhythms, access, capacity, queue, and response time only when play can notice the difference.

Use a Domain Module only if the institution has enough special procedure to justify one.

“I want an economy”

Do not build a stock exchange unless the game is about one.

Create Resources for commodities or services where supply, demand, access, legality, scarcity, substitution, or route disruption can produce meaningful consequences.

Connect only the markets and dependencies that matter.

The goal is:

storm closes road → shipment fails → bread becomes scarce → player sees higher prices and fewer menu options

not:

every loaf has an individual serial number.

“I want a new magic or power system”

Define the Power System first.

Then build reusable Mechanic Packages.

Then Abilities and Techniques.

Then connect actual Characters and Creatures.

Finally ask what the existence of this power changes socially, politically, materially, and culturally.

If nothing in the world changed because magic exists, you probably wrote a combat feature rather than a power system.

“I want a new species or creature family”

Use Creature for the general species or repeatable entity.

Give it habitat, behavior, capabilities, limitations, ecology, and setting role.

Create individual Characters only for members who become individually important.

“I want history to matter”

Record objective Events when they earn independent importance.

Use Location Memory for place scars.

Use Living Memory for subjective experience.

Use Reputation for audience perception.

Use Legacy when the consequence outlives the immediate situation.

Use Era, Inherited World, Descendant Line, or Successor systems only when campaign scale actually reaches them.

“I want something LWE does not currently model cleanly”

First ask whether existing owners can represent it.

Then ask whether a Mechanic Package is enough.

Then ask whether a Domain Module can provide specialist procedure without creating new canonical state.

Only after those fail should you consider a new file type or universal schema field.

At this stage of LWE, new architecture should solve real cross-world failures, not hypothetical neatness.

Build outward. Keep the roots clean.

Builder Assist shortcuts

You do not need a new system for every maintenance job. Orbit can use the existing files more directly.

“Make this LWE-native.” Select an existing record. Orbit should preserve what is already authored, fill only safe setting-valid gaps, and separate anything that needs your creative decision. This is especially useful when a Character needs real routines, a Location needs lived rhythms/services/routes, or a Faction needs enough capacity/dependency structure to move independently.

“Complete this region / folder.” Orbit inventories the scope first, identifies repeated safe gaps, and works in bounded batches. It should not rewrite already-good prose, wander into unrelated folders, or manufacture records to make the project look fuller.

“Health Check.” This is a read-only practical scan, not release certification. It summarizes Integrity, LWE Coverage, Living World, Player UX, Terminology, Privacy, Art, and Publish readiness. Nothing is fixed or generated unless you ask afterward.

“Preview this module.” Before enabling a module, Orbit should explain what it actually contributes, what it depends on, what players would notice, and what world data you need to provide. Previewing does not activate it.

These are workflow conveniences. They reuse LWE's existing owners, Setup state, and validation rules. There is no QoL file type hiding behind them.