Use cases · Fantasy authors

Your world outgrew your notes.

You are forty chapters into an epic, and the world has started disagreeing with itself: a substance that was warm to the touch is suddenly frozen, a faction that never held office is issuing decrees, a character's eyes changed color between books. The lore lives in three documents and your head, and none of them check each other. Loreon is built for exactly this — a structured story bible your prose is read against, so an invented world stays consistent while you write it.

The pains

What breaks in a big invented world.

Fantasy asks you to hold more than one head comfortably holds — and to keep it all consistent across a hundred thousand words or more. Three failures recur:

  • World-bible sprawl. The bible becomes a wiki nobody rereads — pages of lore scattered across a doc, a spreadsheet, and a folder of notes, none of which the manuscript is ever actually checked against.
  • Magic- and world-rule drift. The one rule the plot rests on — what the magic costs, what a substance does, who a law binds — quietly bends to whatever a later scene needs, and no one notices until a reader does.
  • A cast, cultures, and a timeline that won't sit still. Dozens of names, several peoples with their own customs, and an order of events that has to survive being put on a real calendar.

The mechanisms that serve you

Canon the software actually reads.

The fix is not more discipline — it is a bible built so software, not just you, can read it. Loreon holds your world as structured canon: characters, locations, cultures, and the world's rules and history, each its own kind of entry, cross-linked to your prose as you type. Then, when you ask, a per-scene consistency check reads the scene you are in against that canon and posts what it finds to the margin — it never edits your prose, and it never runs behind your back.

  • Rules as entries, not vibes. A substance or a magic system carries its rules as canon, so a later chapter that breaks one has something to be caught against. The method, tool aside, is in how to create a story bible.
  • Drift caught while it is cheap. Continuity is easiest to fix in the scene you are writing, not in a revision six months later — maintaining continuity walks through the discipline the check automates.
Bloodglass
Substance · rule-bearing entry

A volcanic glass that stays warm to the touch on the coldest nights — the tell that it is not ordinary stone, and the fact the whole plot leans on.

Rule Warm even in a hard frost; never freezes
Caught A later scene that ices it over — flagged against this entry

A world rule held as canon is a rule the software can check the prose against.

Common questions

Fantasy, specifically.

Is Loreon only for fantasy?

No — it is built for any long-form fiction where continuity is hard, from science fiction to historical to mystery series. Fantasy just tends to have the most invented rules to keep straight, which is why the fit is so direct.

Do I have to build the whole world bible before I write?

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

What about my magic system's rules?

A rule-bearing thing — a substance, a system, a law — is its own kind of entry that carries its rules, so when the prose bends one, a consistency check or a whole-manuscript validation has something to measure it against.

Loreon · The Writing Studio

Keep the world straight while you build it.

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