Features · Story bible

A story bible your prose is checked against.

The short answer: a story bible in Loreon is not a wiki you maintain on the side. It is structured canon — characters, locations, cultures, and the history and rules of your world — that lives inside the project, cross-links as you type, and is what every consistency check and validation run reads your manuscript against.

What lives in it

Structured, not free-form.

Each kind of story fact is its own kind of entry, so the bible stays queryable instead of becoming one long document nobody rereads. A character carries facts, relationships, and voice; a substance carries rules; a faction carries reach and money. The structure is what lets software — not just you — read it.

  • Characters, locations, cultures — and the history and rules of your world, each held as its own kind of entry.
  • Cross-links surface as you type. Write a name and it binds to its canon entry — no tagging, no upkeep ritual.
  • Canon, not commentary. Entries are the facts your prose is checked against, across chapters and volumes.
Mira, the Northern Courier
Character · secondary · vol. I–II

Courier on the northern routes into Vellhark. Left a sealed letter in Tarsil's keeping and vanished before the thaw.

Carries Messages too sensitive for the guild's own runners
Last seen The Long Quay, two days after midwinter

A canon entity: one kind of entry among characters, locations, cultures, and the rules of the world.

In the studio

The bible, on a real project.

This is the story bible of a working two-volume project — structured entries the editor cross-links as you write, and the canon that validation reads the manuscript against.

The Loreon story bible for a two-volume fantasy project, showing a world-cosmology entry and three character entries in the canon grid

Where entries come from

Built with you, grounded in the book.

Start from a premise and Loreon's writers' room generates a starter bible you shape from there — or import a manuscript you already have and grow canon out of the text itself. When a check turns up a fact and you accept it into canon, the entry records the passages it came from. The bible is grounded in the book, not in notes maintained beside it.

Common questions

Working with the bible.

Do I have to fill it in before I can write?

No. Generate a starter bible from a premise, import an existing draft, or begin with a handful of entries — the bible grows as the book does, and reading, writing, and editing are always free.

I already have a manuscript. Can it come in?

Yes — upload a .docx, .md, or .txt file, or paste your text, and Loreon splits it into chapters and scenes you can edit and validate.

What happens when my prose contradicts the bible?

That is the point of keeping canon structured: run a per-scene consistency check while you work, or validate the whole manuscript before a revision pass — findings cite their passages, and you resolve or dismiss them.

The bottom line

Canon that works for its keep.

A bible nobody checks is a wiki. Loreon's story bible earns its place because the software reads it: cross-links as you type, consistency checks on ask, and whole-manuscript validation on demand — and one bible holds a whole series, so a later volume writes against the same canon. See pricing — the editor and the bible itself are free; credits meter only the agent work.

Loreon · The Writing Studio

Try it on your own manuscript.

The editor is free, and welcome credits cover your first real agent work — no subscription, no card on file.