Skip to main content

🏛️ Notaepedia

A living encyclopedia — automatically written by Sage using everything your room knows about its world. Every character, place, event, and idea gets its own article, cross-linked and always up to date.

🔬 Alpha feature — requires Notaepedia Alpha access
📖

What is Notaepedia?

A Notaepediais a Sage-generated encyclopedia attached to a Study Room. It turns the room's structured World data — characters, places, events, objects, and context entries — into polished, encyclopedic articles that any room member can read.

Think of it as the published reference bookfor your room's world. Where the Worlds system stores raw facts, the Notaepedia presents them as confident, readable prose — the same way a real encyclopedia synthesises facts into an authoritative entry.

🤖 Sage-authored

Articles are written by Sage using entity data, entity links, and cited source material the room has collected. Not templates — actual prose.

🔗 Cross-linked

Every article links to other entities in the same room. Mention a character in a Place article and it becomes a live link to that character's entry.

🔄 Always current

When your World data changes — a character is updated, a new relation is added — affected articles are marked stale and can be regenerated with one click.

📥 Exportable

Export the entire Notaepedia as a structured epub file — readable in any e-reader, offline, and forever.

ℹ️Notaepedia is a room-level feature— each Study Room has its own independent Notaepedia built from that room's World. Different rooms studying the same book, for example, will produce different Notaepedias reflecting each community's perspective and annotations.
⚙️

How articles are generated

When a room owner or moderator clicks Generate Notaepedia, Sage works through every entity in the room's linked World and produces one article per entity. Here is what Sage reads for each article:

🧬

Entity data

The entity's name, type, description, aliases, confidence score, and all custom attributes defined in the World editor.

🔗

Entity relations

Every relation linking this entity to others — family ties, rivalries, locations, causal chains, and anything else the World tracks. Relations give articles their narrative depth.

🌐

Cited source links

Web links, documents, and posts the room has cited as evidence for this entity. Sage uses these to add sourced detail and hedges claims appropriately when sources are sparse.

🏛️

Room context

The room's name, topic, and World name — so Sage understands the genre and tone. A fantasy novel room gets fantasy prose; a historical research room gets careful academic hedging.

Sage follows strict rules for all Notaepedia articles:

  • ✦ Third-person, encyclopedic tone — no first-person, no chat language
  • ✦ Confidence-hedged language when facts are uncertain (e.g. “reportedly”, “believed to have”)
  • ✦ Cross-references use [[Entity Name]] syntax, automatically converted to live links
  • ✦ HTML output — headings, lists, and blockquotes render properly in the reader
  • ✦ No hallucinated facts — only what the World data supports
💡Generation runs on Sage AI credits. A room with 50 entities will use roughly 50 credit operations. Check your credit balance before generating a large World.
🗂️

Entity types

Notaepedia organises articles into five categories, each shown as a section in the left navigation panel. These match the entity types in the Worlds system:

👤 Character

People, fictional characters, historical figures, and any named individual. Sage produces biographical prose covering background, relations, and key events.

Examples

  • Sherlock Holmes
  • Lady Macbeth
  • Jane Eyre

🗺️ Place

Locations, settings, regions, and physical spaces. Articles cover what happens there, who inhabits it, and its significance.

Examples

  • 221B Baker Street
  • Hogwarts
  • Victorian London

⏱️ Event / Timeline

Moments in time — battles, ceremonies, discoveries, and turning points. Sage situates each event in the narrative timeline.

Examples

  • The Battle of Hogwarts
  • The Murder of Roger Ackroyd
  • The Founding

📦 Object

Artefacts, items, weapons, and symbolic objects. Articles trace the object's history, significance, and ownership.

Examples

  • The One Ring
  • Excalibur
  • The Maltese Falcon

💡 Context

Concepts, systems, factions, and background lore that don't fit any of the above. Context entries give articles a place to explain the world's rules and structure.

Examples

  • The Magic System
  • The Political Factions
  • Victorian Class Structure
💡The richer your entity data — more relations, more source links, fuller descriptions — the longer and more authoritative Sage's article will be. Sparse entities produce short stubs.
🖥️

The three-panel layout

The Notaepedia reader uses a three-panel layout designed for exploration:

Left

📑 Table of Contents

Every entity in the room's World appears here, grouped by type (Characters, Places, Events, Objects, Context). Use the search box to filter instantly. A small amber dot next to an entity name means that article is stale and may not reflect the latest World data.

Room owners and moderators see a Generate Notaepedia button at the bottom of this panel — clicking it regenerates all articles for the room.

Centre

📄 Article

The selected entity's full Notaepedia article. It renders rich HTML — headings, lists, blockquotes, and live cross-reference links to other entities. Scroll down to see the moderator notes section if the room has added editorial annotations.

If the article is stale, a yellow banner appears at the top explaining what changed and offering a regenerate shortcut.

Right

🔍 Details & Related

Shows entities that are cross-referenced in the current article, generation metadata (date and version number), and links to export the whole Notaepedia as an epub. Moderators also see a per-article regenerate button here.

ℹ️The URL updates as you navigate — each entity has a permanent address at /study-rooms/[slug]/notaepedia/entity/[entity-slug]. You can link directly to any entity article from chat, posts, or outside the platform.
📊

Confidence levels

Every entity in the Worlds system has a confidence score from 1 to 5 — set when the entity is created or updated. Sage uses this score to calibrate the tone of the article.

ScoreLabelSage's approach
1RumourHeavy hedging — “reportedly”, “alleged”, “some sources suggest”
2UncertainModerate hedging — “appears to”, “believed to be”
3PlausibleLight hedging — mostly plain statement with occasional qualifiers
4ConfirmedConfident, declarative prose — no hedging
5CanonicalAuthoritative — treats the fact as definitively established, like a published encyclopedia entry
💡Before generating your Notaepedia, review your entity confidence scores. Entries left at 1 or 2 will produce heavily hedged articles. Bump confirmed facts to 4 or 5 in the World editor first.
🔗

Cross-references

Notaepedia articles link to each other automatically. When Sage writes an article about a character, it wraps related entity names in [[double brackets]]. These are converted into live links during generation.

For example, if an article about Inspector Lestradementions Sherlock Holmes and 221B Baker Street, those names become clickable links that jump directly to those entities' articles.

Example — generated article snippet

Inspector Lestrade served as a detective inspector of the Metropolitan Police during the late Victorian era. He frequently collaborated with Sherlock Holmes of 221B Baker Street, though their relationship was often characterised by professional rivalry and Lestrade's scepticism of Holmes's unconventional methods. According to Dr Watson's accounts, Lestrade was nonetheless privately grateful for Holmes's interventions.

Amber underlined names are live cross-reference links

ℹ️Cross-references only link to entities that exist in the same room's World. If Sage mentions an entity that has no article yet — because it was added after the last generation — the text remains plain until the next full regeneration.
🕰️

Staleness — when articles go out of date

A Notaepedia article becomes stale whenever the World data it was built from changes. Specifically, an article is marked stale when:

  • ✦ The entity's name, description, or attributes are edited in the World editor
  • ✦ A relation involving this entity is added, changed, or removed
  • ✦ A source link that was cited for this entity is updated

What you'll see

  • 🟡 A small amber dot in the left navigation panel next to the entity's name
  • 🔔 A staleness banner at the top of the article listing what changed (e.g. “Entity data updated”, “Relations changed”)

A stale article is not hidden or removed — it stays visible to all members. It simply signals that the content may not reflect the latest World data. The old article is often still useful to read while you wait for regeneration.

💡You can regenerate a single stale article from the right panel (moderators only), or regenerate all articles at once from the Generate button in the left navigation panel.
✏️

Moderator notes

Room owners and moderators can add moderator notesto any article — without affecting the Sage-generated body. This is the place for editorial additions that Sage can't produce on its own:

  • ✦ Community-specific interpretations of the entity
  • ✦ Disputed details that members should be aware of
  • ✦ Spoiler warnings or reading-order guidance for book clubs
  • ✦ Links to specific discussions in the room chat or posts
  • ✦ Corrections to Sage's article pending a full regeneration

Important rules

  • 🔒 Moderator notes are never overwritten during article regeneration — they are stored separately from the Sage-generated body
  • 👁️ Notes are visible to all members who can view the Notaepedia (same visibility as the article itself)
  • ✍️ Only owners and moderators can add or edit notes — regular members cannot
ℹ️To edit moderator notes, scroll to the bottom of any article. An editable text area appears for owners and moderators. Click “Save notes” when done — the page updates immediately without a full refresh.
👁️

Visibility settings

The room's Notaepedia has a single visibility setting that controls who can read all articles. Room owners configure this from the Notaepedia config panel.

🔒 Draft

default

Only room owners and moderators can see the Notaepedia. Articles can be generated, reviewed, and edited before any member sees them. Default state for all new Notaepedias.

👥 Members

Any room member can read the Notaepedia. Useful for community book clubs where the Notaepedia is part of the membership experience. Non-members cannot access it — even for public rooms.

🌍 Public

Anyone — including people who are not members of the room, and users who are not logged in — can read the Notaepedia. Useful for fan wikis, research archives, and public lore bibles. The room itself does not need to be public for the Notaepedia to be public.

⚠️Changing visibility to Public means anyone can find and read your Notaepedia. Make sure moderator notes do not contain spoilers, private discussions, or sensitive information before going public.
📥

Epub export

The entire Notaepedia can be exported as a standard EPUB 3 file — readable in any e-reader, including Kindle, Apple Books, Kobo, and the NotaeLibrary reader.

What is included

  • ✦ A preface listing the room name and export date
  • ✦ One chapter per entity, ordered by type then name
  • ✦ Entity type and confidence score displayed under each heading
  • ✦ All moderator notes as a separate section within each chapter
  • ✦ Generation date and version number for each article
  • ✦ A full EPUB 3 table of contents

Cross-room links

Links to entities in other rooms cannot work in a standalone file. They are converted to plain text references in the format Entity Name [notaelibrary.com/...] so the original source URL is preserved.

To export, click the Export as epub link in the right panel of the Notaepedia reader. The file downloads immediately — no email, no waiting.

🚀

Step-by-step: your first Notaepedia

You need to be a room owner or moderator with the Notaepedia Owner feature enabled. If you do not have it yet, contact your platform administrator.

1

Make sure your World has entities

Go to your room's World section and confirm you have at least a handful of entities. The richer the World — more entities, more relations, better descriptions — the better the Notaepedia will be. You can add entities at /study-rooms/[slug]/world.
2

Review entity confidence scores

In the World editor, check that key entities have their confidence scores set appropriately. Facts you are certain about should be at 4 or 5. Rumours and unconfirmed details should be 1–2 so Sage hedges them correctly in the article.
3

Navigate to the Notaepedia

Go to /study-rooms/[slug]/notaepedia — or look for the Notaepedia link in the room navigation. The page will show an empty state on first visit.
4

Click 'Generate Notaepedia'

The Generate Notaepedia button is in the bottom of the left navigation panel (visible to owners and moderators only). Click it and wait — Sage will work through all entities one by one. A counter shows progress.
5

Review the generated articles

Read through the articles. Check for anything that looks wrong — Sage sometimes makes plausible-sounding errors when entity data is sparse. Use Moderator Notes to annotate anything that needs clarification for readers.
6

Set visibility and publish

Once satisfied, open the config panel and change visibility from the default Draft to Members or Public. Members will see a Notaepedia banner on the room lobby prompting them to read it.
💡Generation runs article by article in sequence. If a room has 80 entities, it may take a minute or two. You do not need to stay on the page — come back later and all articles will be ready.

FAQ & limitations

Can regular members edit articles?

No. Only room owners and moderators can edit moderator notes or trigger regeneration. Regular members can read articles and follow cross-reference links, but cannot alter any content.

Can I edit the Sage-generated body directly?

Not currently. The generated body is Sage's output and is intended to reflect the World data faithfully. To change what Sage writes, update the underlying entity data in the World editor and regenerate. For annotations, use Moderator Notes.

What happens if I regenerate — do I lose my moderator notes?

No. Moderator notes are stored separately from the generated body and are never overwritten during regeneration. You will never lose notes by regenerating.

How many articles can a Notaepedia have?

One per entity in the room's linked World. There is no hard cap — a World with 300 entities will produce 300 articles.

Can I have a Notaepedia without linking a World?

No. The Notaepedia is built entirely from World entity data. If your room has no World linked, there is nothing for Sage to generate from.

Does the Notaepedia update automatically when the World changes?

Articles are marked stale automatically when World data changes, but they are not regenerated automatically. A moderator or owner must trigger regeneration. This is intentional — automatic regeneration on every edit would be expensive and could overwrite carefully reviewed articles.

Can I link to a Notaepedia article from a post or chat message?

Yes — every article has a permanent URL. Copy the URL from your browser and paste it anywhere. People with access to the Notaepedia can follow the link directly to that article.

Is the epub export the same as the online version?

Almost. The epub includes all generated body text and moderator notes. Cross-room reference links are converted to plain-text URLs. The epub does not receive automatic updates — re-export after regenerating to get the latest version.

➡️

Where to go next

Ready to build your room's encyclopedia?

Go to your Study Room's World section and start adding entities — each one becomes a Notaepedia article.

🏛️ My Rooms →