Field notes / Worldbuilding
A world bible that earns its pages.
A world bible becomes useful when it changes what you can write. Begin with the smallest record that can hold a scene together. Expand it when the story asks for more.
Start with the promise, then the constraint.
Write one sentence about the experience the world should create. Awe, uneasy discovery, intimacy or adventure can each support a different design. Then write a rule that forces a cost. A rule with no limit gives a character too many exits; a cost creates a choice.
In the free demonstration, a coastal city's archive can restore a damaged memory, but the person making the repair loses an equally specific memory of their own. This is a proposed example outside official Arcanea canon. Its usefulness comes from the consequence: the archivist cannot save everything without giving something up.
Make the rule visible in one scene.
Choose a character with a present desire. Give them a reason to resist the world rule and put a decision in front of them. Draft the scene before writing ten pages of history. If the scene works only after an explanatory lecture, simplify the rule or make the consequence easier to observe.
Record what the reader actually sees: an altered object, a failed action, a missing name or a relationship changed by the decision. That evidence becomes the standard for later scenes. The reader should encounter the world's behavior before receiving a catalogue of its institutions.
Keep a small set of connected records.
The first world bible needs a promise, rule, cost, protagonist, place and proof scene. Give each a stable identifier. A character record names their desire and constraint; a location record says what actions it enables or prevents. Link the scene to the rule it demonstrates and the character it changes.
Separate your source notes from accepted facts and generated proposals. A plausible suggestion from a model is still a suggestion. A contradiction record should identify the two conflicting claims and the scenes affected. That makes a deliberate revision possible without silently rewriting the whole world.
Choose visual signals you can review.
Describe materials, light, shapes and recurring forms. 'Beautiful fantasy city' provides little direction. Salt-clouded glass, narrow tide stairs, copper repairs and low morning light give an illustrator or image workflow details that can be accepted or rejected.
Keep the visual brief separate from the final artwork. An image may inspire a new proposal, but it cannot establish a new world law by itself. When a visual detail matters to the story, record the decision in the same continuity ledger as the text.
Export something another person can use.
A portable packet can be plain Markdown and JSON: the current brief, entity records, accepted facts, open conflicts and the proof scene. State its version, file contents and rights. Another writer or artist should be able to tell which material is binding and which is open for revision.
Avoid building a complete encyclopedia before the first scene has passed review. Add timelines, factions and maps when they resolve a real production question. The practical test is simple: does this page help someone make the next scene consistent, emotionally active and specific?
Try the worked example.
Read the free demonstration scene and download the editable World Starter. The example is an AI-assisted proposal outside official Arcanea canon; adapt its method to your own original project.
Open the free World StarterInspect the Production Edition