World

Lore files the world as searchable entries: calendars, factions, rules, terms, historical events. The reason is practical—the agent reads these before it speaks, and by chapter twenty you stop re-explaining what “the return of spirit energy” means.

Entries are not sticky notes. The draft and long text can cite them, leaderboards can rank them, and the faction category doubles as the source of truth for who belongs to what.

Three uses come up most:

• Write a rule as one entry. A question-and-answer card such as “what does the return of spirit energy cost” travels with continuation and consistency checks, so the model is not inventing a power system for you.
• Write a term with aliases. The draft uses the short form, the entry keeps the full name, and search finds either side.
• Write a faction as one entry. Members, aliases and leaderboard scope all hang on that card, and it is also the answer to “who does this character belong to”.

Open World in the left navigation. Beside the title is the entry count; the toolbar has search (name / description / alias), a category filter (All Categories plus the five fixed ones), sorting (Newest Created, Sort by Name, By Category, Member Count) and the create button. Cards show “No description yet…” when empty, and carry alias and evolution counts.

The standing sidebar on the right holds Leaderboards. Characters, locations, props and world entries all share this one system—it belongs to the World page rather than to each module separately.

1. 1
   Create

   Open the create button and fill Edit Settings: name, category, Aliases/Abbreviations (Enter to add), description.
2. 2
   Cite other objects inside the description

   The description is a long-text reference field: type @, search characters, places, props or other entries, and the citation shows in place as a recognisable tag. Clicking jumps; there is no second preview box below.
3. 3
   Save

   Save at the bottom. The list, search hits and the context AI reads all follow at once.

Schools, houses, courts, organisations—these are lore entries categorised as factions, and the card is the single source of truth for the name, aliases and identity. A character stores the card’s identity, not a word, so renaming updates chips, roster groups, member counts, leaderboards and what the agent reads together.

Create factions here. The “create faction” shortcut on a character card exists to make the same thing quicker, not to leave a loose name string behind—what lands in the project is still this card.

The sidebar head has board selection, New Leaderboard and delete; Expand Leaderboard and Hide Leaderboards fold the block away. A new board first asks what it ranks: characters, places, props and settings are isolated kinds, and each can hold several boards of your own.

• Scores are yours to type; higher ranks first. Position, score, ties and back-references are recorded against stable object identity.
• A character board can be scoped: in Manage Leaderboards pick a faction (Applicable Factions, one at a time) and only characters in it enter. Renaming the faction leaves the condition intact; deleting the card or leaving the faction category clears the condition in the same cascade and falls back to all characters.
• Board names rename in place (Double-click to rename). With no boards you see No Leaderboards; an empty board says No content to rank.

A leaderboard is an author’s judgement, not a statistic. Appearance Count and narrative weight are not ranked here—they live in the prop list’s sorting and the numbers on character cards.

Ask for “a rule entry for the return of spirit energy, state the cost”, and the confirmation card can create an entry (name, category, description, optional aliases), change the base fields, replace the whole description, or delete the entry. Category must be one of the five, and name and description cannot be empty. Up to 8 operations per card, one undo afterwards.

• Lore cards no longer take new per-chapter tracks. Existing ones from older projects sit in a collapsed read-only compatibility area: still visible, still exported, not writable from the new interface. Chapter evolution stays on the supported character and prop fields.
• An @ citation only handles reading jumps. It is not faction membership, place parentage or a scene setting location—those have their own fields.
• An ordinary noun with no citation behaves like an ordinary noun: it does not jump and is not counted in member counts or boards.
• If the card to save cannot be found, the drawer says so rather than quietly creating a duplicate.

Full reference rules are in Entity mentions and @.