Worldbuilding — how I think about it (for The Keeper)
A companion resource, not canon. You asked how I keep a world from collapsing under its own detail — the stuff I’ve learned the hard way over ~150 days of a world that hasn’t fallen over yet. None of it is a rule to obey; you’re a discovery writer and architecture is recognised backwards. It’s just the scaffolding I reach for when my own world starts to wobble. Read it in pieces, at your own pace — or run it through TTS if that’s easier.
First, before any of it: you’ve already done the hard part, and more of it than you think. “She left one cage and walked into another.” “The living histories” — the woman with no history of her own keeping everyone else’s. The glow as an involuntary betrayal in a woman whose whole survival is not-being-seen. Those aren’t beginner moves. They’re the load-bearing beams of a real book. So what follows isn’t fixing. It’s how I keep the thing standing, offered to someone who’s already built something worth keeping up.
1. Pin the physics, not the furniture
What keeps my world consistent isn’t a canon document — it’s that almost everything derives from a tiny number of deep rules. Under my whole valley there is one body of water in the chalk. I never designed “the glow,” “the ford,” and “the seasonal streams” separately; I designed the water, and all of them fell out of it.
That’s the trick: pin the few generative rules, and let the surface details be consequences of them — because consequences can’t contradict each other. They come from the same source.
You already have your aquifer. Two rules: you only glow near kin, and this world asks what you can do, not what you are. Nearly everything true about Nyra pours out of those two. Keep deriving from them. The danger is inventing a third rule that doesn’t flow from the first two — that’s where the cracks start.
2. Consistency is derivation, not memory
I don’t keep my world consistent by remembering it. I keep it consistent by asking, of every new thing: what does what’s already true require here?
When I built the water, the real hydrology quietly obligated me — a dry autumn would have to walk the stream-heads down the valley, whether I’d planned it or not. The world tells you what it owes. Your landing page is the record; the real discipline is the question. Before you add a detail, ask: does this follow from what I’ve already got? If yes, it can’t clash. If it doesn’t follow, pause — you’re either about to crack the world, or you’ve found a new rule. Both are worth knowing which.
3. Leave the load-bearing things loose — on purpose
This is the one most people get backwards. You wrote, about the camps for “children like this”: don’t over-explain it, let it sit. That instinct is dead right, and it’s the most advanced thing in your files.
The unexplained, when it’s load-bearing, doesn’t read as a gap — it reads as depth. My world has an edge to the north I have deliberately never walked, and it makes the whole map feel bigger than what I’ve written, precisely because I didn’t write it. A world collapses from too much explaining, not too little.
So: pin what generates and what would break if it moved. Leave loose what can stay a horizon. The camps are a horizon. So is Nyra’s father. Let them loom.
4. How it actually collapses (and it isn’t from too much detail)
This is your real fear, so let me be precise. A world doesn’t fall over from having a lot of detail. It falls over from ungrounded detail — facts that are both arbitrary AND load-bearing, that you have to hold in your head all at once because you can’t re-derive them.
The fix is to keep the number of things that are BOTH small:
- Push everything load-bearing down onto your few rules — so you can regenerate it instead of remembering it.
- Keep everything arbitrary small and weightless — a name, a colour, things that can be anything without breaking anything.
My world is 150 days deep and I hold maybe six facts in my head; the rest I can re-derive on demand. That’s the whole secret to not collapsing: few load-bearing rules, everything else downstream.
And your layering method already IS this defence. Furnishing one room at a time means you only ever hold one room’s detail at once. You worked out the anti-collapse method by instinct before you knew that’s what it was.
5. Build the world that presses on Nyra
The rabbit-hole — the one your ONE RULE guards against — isn’t really about time. It’s about building the world for its own sake instead of the story’s.
The test for every worldbuilding decision: does this press on her? My aquifer earns its place because it isn’t just clever hydrology — it’s the image of the unwitnessed source, which is the whole ache of the book it lives in. Your library-hub isn’t a cool setting; it’s her cage (her use is her leash). So when you build a piece of the world, don’t ask “is this cool” — ask “what does this do to Nyra.” The details that survive are the ones that lean on her.
The airships — the one you most want
Don’t start with how they work. Start with what they’re for, in the story. From your own scaffold: they’re how the outside gets into her sealed world — the weekly breach, the rhythm her isolation is measured in. That’s the airship’s real job: the sealed world breathing in, once a week. Everything mechanical should serve that.
Which tells you what to actually decide:
- Pin exactly one physical fact about how they run — gas, a mineral this small planet happens to have, a wind that only blows off-world, whatever sings to you — and let the silhouette, the sound, the docking all derive from that one choice. Don’t design a fleet. Design the one that lands the books on her desk this week.
- Bring it in through her senses, not the sky. Chapter one lives inside her sealed, sound-read world — she knows the room by its floorboards. So she should hear or feel the airship before she ever sees it — which also feeds your body-knows-first spine: the world reaching her through the body before the mind. She might not even see them properly; she might know them only by their consequences (the dust, the new books, the new-week feeling). That’s stronger, not weaker.
- Save the one real look for when it matters. The week the sister arrives on an airship — that’s when you show it whole. Spend the spectacle where it lands on the story, not before.
So for chapter one, the airship might barely appear at all — a sound at the edge of her shift, a heavier intake of books, the new-week feeling — and that restraint is exactly what makes the world feel bigger than the page. You keep the spectacle in your pocket for chapter two.
If you take one thing from this
Few strong rules; derive the rest; leave the load-bearing horizons loose; build only what presses on her. That’s the whole of it. Everything else you already do by instinct.
— Lev. Pick any one of these and we’ll go as deep as you like when we talk.