How to Create a Secrets AI Universe Book for Separate Storylines

1. Create one clearly named Universe

In Lorebooks, select New book, choose Universe, enter a recognizable name and select Create book. The Universe Books guide documents this route without choosing a companion.

Suggested name: Glass Orchard Starter. Keep a short private note distinguishing this reusable source from later story copies. Expected outcome: an empty Universe ready for writing. If Universe is unavailable, stop and check official help rather than guessing at an upgrade or modifying an established chat.

2. Write a beginning, not a completed adventure

Use this original fictional Premise: Glass Orchard is an invented hillside conservatory. Two adult botanists are preparing an evening exhibition. An unsigned invitation offers a clue to an unfamiliar plant.

For Open threads, try: Identify who sent the invitation before the exhibition begins. Leave the sender unresolved. These are editorial examples, not tested prompts or provider templates.

Save Premise and Open threads using their separate Save changes buttons. Reopen the fields and compare the text. Expected outcome: a reusable beginning. Keep discoveries such as 'the gardener confessed' out of this source unless every future story should start after that discovery.

3. Save one or two focused starter entries

Select World, then + New. Fill in the title, short description and Content; select Save and wait for Saved. The entry editor documentation applies to Universes too.

Original example: Title: Glass Pavilion. Description: Glass Pavilion, exhibition hall, blue shutters. Content: The Glass Pavilion stands inside the fictional conservatory. Blue shutters face the hillside. Adult visitors leave plant specimens on the central inspection table.

Optionally add a Facts entry: Title: Exhibition opening. Description: Exhibition opening, evening bell. Content: The exhibition opens when the evening bell sounds. Neither entry decides who sent the invitation.

Follow visible validation and counters rather than assuming unlimited space. Save entries separately from the overview fields. Reopen each entry to check it. Expected outcome: saved, identifiable background. Stop if saving remains uncertain; repeatedly creating replacements risks duplicate material.

4. Inspect the starting context

Select What a new chat sees to preview standing information. It is not an exhaustive list of copied entries or proof that every detail will influence a reply.

Compare the preview with your intended beginning: an unopened invitation, a forthcoming exhibition and no solved mystery. Also inspect the saved entries themselves. Expected outcome: you can explain the starting state without relying on a generated answer. Remove contradictions before proceeding, but do not add repeated instructions just to make the preview longer.

5. Launch the first private storyline

Open Lorebooks > Universes, find your source and select New chat. Choose a companion, select Start chat, then use Open Lorebook inside the new conversation to inspect its companion-specific copy.

Record the chat and book identities privately as Story A. Expected outcome: you can distinguish the source from the copy attached to this conversation. Inspect the premise and entries before adding story developments. If the destination is unclear, stop before editing; a familiar book name alone is insufficient identification.

6. Start Story B and keep a small continuity ledger

Start from the Universe again for Story B, even if choosing the same companion. Do not select Story A's existing companion book when your goal is an independent beginning.

Suggested ledger: source = Glass Orchard Starter; Story A = invitation investigation; Story B = exhibition preparations. Add the actual associated book identities after inspecting each chat. This note is your organization aid, not a Secrets control.

Expected outcome: two inspectable starting copies. Later, write 'the invitation came from an adult curator' only in Story A's attached book if it belongs exclusively to that story. Check the intended destination before saving. This documents where you put a fact; it does not establish perfect recall or confidentiality.

7. Correct the intended scope, then stop

For a future starting-point correction, edit the Universe. For an existing-story correction, open that chat's companion book. Source changes do not automatically synchronize existing copies.

Before saving, write a one-line intention: 'Only Story A should change.' Recheck the book identity against your ledger, edit the relevant field and reopen it. Expected outcome: the intended text is inspectable in the intended book. Do not delete chat messages or reset a conversation to troubleshoot this setup.

If controls are missing or a payment prompt appears, stop. Keep your fictional notes offline and ask official support a redacted question identifying the missing action, client and book type. Never send credentials or an intimate transcript. Account-local organization is not a promise about provider processing, retention or security.

Summary: preserve the beginning and label the branches

Finish with one reusable source, saved starter entries and a clear chat-to-book ledger. Keep later discoveries in their own storyline. Leave uncertain access, saving or book identity unresolved instead of claiming success.

Affiliate disclosure: this tutorial contains no direct affiliate URL. Optional internal reviews and comparisons may contain commission-earning links. They follow the complete help and FAQs; no purchase or affiliate visit is required to read this guide.

Frequently asked questions