Getting started

Loretia is your story's memory. She reads a screenplay, novel, or branching script, remembers every character and detail, and tells you when something doesn't add up — a dead character who reappears, an alibi that slips, a promise the story never keeps.

There are two ways to work with her:

• The dashboard — sign in, drop in a file, and watch her build a living story bible.
• The standalone CLI — run the whole engine on your own machine, with your own AI key, no account required. Great for writers who live in the terminal and for CI pipelines.

Your first check (dashboard)

1. Open the dashboard and create a script.
2. Paste or upload your draft (Final Draft, Word, Markdown, PDF, or a Twine game).
3. Loretia reads it, tracks everyone in it, and flags anything that breaks continuity.

Your first check (CLI)

# Point Loretia at a file — she reads it locally and prints a continuity report.
lore analyze chapter1.md --model-key sk-or-...   # your OpenRouter key

She exits non-zero when canon breaks, so the same command works in a pipeline. See Standalone CLI for the full command set.

What she looks for

Loretia compiles your prose into a strict timeline of facts and checks it for contradictions: a character acting after they've died, two incompatible facts, a setup with no payoff. The rules she applies are described in the NCDL syntax reference.