Lore: Canon, Continuity and More

Canon turns what your bible says into facts with sources. Each fact cites the passage it rests on and the chapter from which it holds. A change never overwrites a fact: the old version is retired and the new one recorded, so every fact keeps its history, and the entry page shows where each one came from.

When the text around a cited passage changes, Lore finds the passage again by its wording. If the passage was deleted or rewritten, the fact is kept and marked as having lost its evidence. You can lock a fact so automatic updates leave it alone, and canon is shared by everyone who works on the project.

On Pro, run an update after a writing session. Lore reads only the chapters that changed since the last run, shows the price in credits before it starts, and puts what it found in the review inbox: new entries, new and changed facts, other names, relations, events, and entries that look like the same thing twice. Every suggestion carries the quote it comes from, checked against your text.

Accept, edit, merge, keep a change as a progression, or reject it with a reason. A suggestion you reject does not come back unless its passage changes, and a decision can be undone. Nothing reaches your canon without your decision. You pay only for the parts of a run that produced verified results.

Continuity Guard compares your manuscript with your canon and lists each problem it finds with the passage it quotes. Its free checks work on every plan: a color, number or family relation that contradicts the bible, a likely misspelling of a name, a character on the page after their death, ages that do not add up, impossible family dates, a point-of-view character who knows something before learning it, story days that run backwards, a relationship used after it ended, stalled plot threads, names too alike, and facts whose cited passage is gone.

For each problem, mark it intentional, update the canon from it, jump to the passage to fix it yourself, or turn it into a task. Lore never rewrites your text, and you can turn any check on or off. On Pro, an AI check finds subtler contradictions when you ask for one, quoting both the passage and the fact it contradicts, with its price shown first.

Story time places your canon in time. Give each scene a story day, with suggestions from phrases like "the next morning", and build calendars with your own months, weekdays, eras and leap rules. Events can be dated in your own calendar.

The time machine shows the bible as of any chapter: entries, the graph, the map, the family tree and the wiki preview show only what is in place by then. The Time tab adds a timeline you can order by story time or by reading order, a legends view of your world's history, and journeys that follow a character from place to place.

On Pro, ask a question about your story in plain words, such as "Who is Mara's sister?", and get an answer built only from your bible and your book. Every sentence cites the fact or passage it comes from, and a sentence without a source is labeled as an inference.

Choose a chapter and only chapters up to that one are read, so the answer cannot spoil what comes later. Choose a point-of-view character to answer from what they know. If nothing in your bible or your book matches the question, nothing is asked and nothing is charged.

On Pro, interview one of your characters as of a chapter you choose. They answer only from your bible and your book, every claim shows where it comes from, and anything they cannot know yet is flagged, for example "Comes in chapter 28".

Nothing from an interview is added to your manuscript or your bible. A line backed by a passage can be sent to the review inbox, where you decide. Each question shows its price before you ask it, a question with no verified answer is not charged, and you can delete an interview at any time.

Put several books in one series and they share characters, places and canon. The series dashboard lists the books in reading order, the overrides each book makes and where the books drift apart, and an entry's page can show it as of a given book and chapter.

Tag your canon, for example "Book 1 published", and compare any two tags. Contradicting published canon becomes an error in Continuity Guard, and changing it asks for a reason, which goes into a retcon ledger you can export as errata. What-if branches let you explore a change, then merge it or discard it.

Decide how far readers of your public wiki can see: readers without a link see up to the chapter you choose. Hand out signed reader links that unlock more, up to a chapter and for a length of time you set, for readers, beta readers or patrons. Nothing after the allowed chapter is ever sent to the reader.

Beta readers can leave comments that show up in your continuity checks. Published entries get their own wiki pages that search engines can find, and you can make a shareable character card from an entry. On Plus, an EPUB export can add an X-Ray: the first mention of an entry in each chapter links to that entry as of that chapter.

As you write, mentions of your entries are underlined in the editor. Hover over one for a card that shows the entry as of the page you are on, and Cmd-click or Ctrl-click a name to open its entry. Type @ or [[ to insert an entry's name, or to create a new entry from what you typed.

Rename an entry everywhere at once: preview the changes in your Lore and in each document, choose which to apply, and the open document changes in a single undo step. Continuity problems show as marks in the page margin, next to the passage they quote.

Lore links into the rest of your project. Map regions and pins, calendar events, ideaboard shapes, and taskboard and corkboard cards can link to entries, and every entry page lists where it appears. Drawing a connection between two Lore cards offers to save it as a relationship.

Insert a saved view into a document as a live list that stays up to date, or an entry as a card. Showing a view in a document is free; saving the view needs Plus. Cover Studio can use your characters' portraits and appearance fields.

Search finds entries and passages by what they mean, not only by the words you type, so a search for "betrayal at the harbor" can find the scene even when those words are not in it. Exact matches always rank first, and every result says whether it matched by text or by meaning.

To do this, Lore keeps a search index for each project that has AI switched on, including projects where you never use an AI feature: in the background, your documents and the AI-visible parts of your Lore are turned into search vectors with Amazon's Titan embedding model on AWS Bedrock. Private notes, entries set to never and fields hidden from AI are never indexed, and the public wiki never uses the index. Turning the project's AI switch off deletes its vectors and keeps ordinary text search. Building the index costs you nothing and uses none of your credits.