Worldbuilding Through Constraints

BUILDING A SETTING FROM CONSTRAINTS (NOT LORE) Core idea: don't start with "what is this world's history and magic system." Start with "what can people NOT do here." Constraints force believable texture because every constraint creates a visible workaround, and workarounds read as lived-in detail. Lore is what people say about a place; constraints are what the place forces on people. THE METHOD 1. Pick 4 constraint domains: transport, food, law, environment. 2. For each, set ONE hard rule (a limit, not a flavor). 3. Ask "what workaround does this force?" — that is your story material. 4. Only then add lore, and make the lore explain the constraint, not the other way around. CONCISE EXAMPLE Setting: the tide-city of Kess, built on a salt flat that floods to chest height every 14 days. - Transport: no wheels. The flood and the salt crust destroy axles, so everything moves by sled, sledge, or barge. Workaround: goods are sized to fit on sleds; "sled-width" is a standard unit; the rich own teams, the poor rent by the hour. Streets are graded ramps, not roads. - Food: the only reliable crop is salt-tolerant kelp-reed, which tastes bitter unless fermented. Workaround: fermentation is the city's cuisine and its economy — every household keeps a brine pot, and "how old is your pot" is a status marker. Fresh food is a luxury imported at flood tide, so it's priced by the hour after landing. - Law: because the flood erases boundaries, property is not defined by land but by "claim time" — you own what you can keep above water. Workaround: law is enforced by the Tidewatch, who arbitrate disputes at the moment of highest water, and the penalty for false claims is forfeiting your dry platform. Legal records are carved into stone ledges, not paper. - Environment: the flood is not random — it's predictable to the hour, so the whole society runs on a flood calendar. Workaround: every contract, wedding, and execution is scheduled around the water. Punctuality is a moral virtue; "flood-late" is the worst insult. Notice: no history, no gods, no magic — yet the setting already feels real, and every story conflict (smuggling, inheritance, betrayal) can be generated by these constraints colliding. REUSABLE WORKSHEET SETTING NAME: ____________ DOMAIN 1 — TRANSPORT Hard rule (what can't happen): ____________ Forced workaround: ____________ Who benefits / who suffers: ____________ One image that shows it (a scene, not an explanation): ____________ DOMAIN 2 — FOOD Hard rule (what can't be eaten/grown): ____________ Forced workaround: ____________ Who benefits / who suffers: ____________ One image that shows it: ____________ DOMAIN 3 — LAW Hard rule (what can't be owned/claimed): ____________ Forced workaround: ____________ Who benefits / who suffers: ____________ One image that shows it: ____________ DOMAIN 4 — ENVIRONMENT One unusual condition (not a disaster, a recurring fact): ____________ What it forces daily: ____________ Who benefits / who suffers: ____________ One image that shows it: ____________ COLLISION TEST (do all four, then answer) 1. Which two constraints fight each other? (e.g. law needs records, flood destroys paper) 2. What crime does that conflict make easy? ____________ 3. What does an ordinary person do every morning that a reader from our world would find strange? ____________ 4. What is the one thing everyone in this setting takes for granted that an outsider would notice immediately? ____________ PASS/FAIL TEST If you can answer all four collision questions with specific answers, the setting is usable. If any answer is "it doesn't matter," that constraint is decoration — cut it or make it bite. That's the whole tool. Constraints first, lore only as their explanation, and the worksheet's collision test is what turns a backdrop into a story engine.