Building Without Overbuilding
The most common way to harm a good world is to build too much of it. Every unnecessary record is a promise to maintain something play may never need.
Know more than you track. Simulate broadly. Persist selectively. Write only what matters.
The world is larger than its files
Your fiction can hold vastly more than your records should. A village contains many people without every resident needing a file. A road exists without a dedicated type. A family tie exists without a genealogy system. A merchant sells ordinary goods without every transaction becoming history. A character remembers something without a universal memory object. Weather matters without a weather simulation. A household eats without recording every meal. A business operates without logging every customer. A war occurs without army and unit systems.
Learn the four separate questions:
- Does this exist in the fiction? Most things do, lightly.
- Is it relevant now? Fewer things are.
- Does it need persistent state? Fewer still.
- Does it need dedicated architecture? Almost nothing does.
Existing, relevant, persistent, and architectural are four different thresholds. Do not treat them as one.
When detail earns persistence
Before recording anything, ask:
- Is this fact consequential — does it change what people can do, owe, own, or expect?
- Is it likely to matter again?
- Does continuity depend on remembering it exactly?
- Does an existing place in the system already represent it?
- Would persisting it actually improve play?
- Is this genuine established truth, or merely an assumption?
If the answers do not justify persistence, leave it contextual. A guess used to color one scene needs no record. A detail that will never be consulted again needs no record.
Detail when consequentially useful. A random baker met once needs no file. The baker who becomes an employer does. A background cottage needs no property record. The cottage purchased does. A passing rumor may stay contextual; a rumor that reshapes relationships or politics leaves its consequences in the appropriate records. A routine workday needs no write; a workplace injury that lasts needs its injury recorded.
Do not build a type for every noun
Fictional concepts do not automatically require system architecture. Roads, religions, cultures, dynasties, armies, claims, memories, rumors, weather, crops, meals, tenancies, titles, and routines can all exist — vividly — through description, existing entities, Project truth, contextual reasoning, or reference knowledge.
A concept is not a mechanic. A concept is not a type. More realism is not more tracking. More detail is not more persistence.
When tempted to create something new, check first: does an existing record already own this? Ownership lives in Property. Work lives in Employment. Belonging lives in membership. Money lives in its separate pools. Almost everything you want to record already has a home.
The cost of overbuilding
Unnecessary state is not free. It means harder navigation, duplicated truth that drifts into contradiction, stale records nobody trusts, heavier maintenance, slower reasoning, wasted preparation, and a game that feels like bookkeeping instead of life.
Keep it practical: every record you create is something you must keep true. Create few. Keep them true. Let the rest live lightly in description until play calls for more.
Good Builder Questions
- "Will play actually benefit from remembering this later?"
- "Does the system already have an authoritative home for this fact?"
- "Am I building this because the world needs it, or because it is possible to track it?"
You Usually Do Not Need...
...every villager, building, road, meal, purchase, rumor, relationship, routine, weather variable, item, memory, work action, traveler, soldier, or political opinion recorded. A living world feels deep because its consequences stay coherent — not because everything is tracked.