Adapting the Engine

Lifeborn Systems is intentionally reusable, but its core assumptions are grounded modern-life simulation, persistent consequences and human-scale competence. A world may narrow or extend those assumptions while preserving the separation of durable state.

Add new file types when a recurring concept genuinely needs structured persistence. Do not create a type merely because a concept appeared once. Prefer extending the world with content before extending the engine with more schema.

Keep the engine layer generic. World-specific people, places, institutions and starting conditions belong to the world built on Lifeborn Systems, while reusable simulation rules and persistence structures belong to the engine.