OD learning library: cross-reference guide

This guide connects 26 beginner lessons, four compact references, and the Companion Toolkit. Start with a learning path, open the matching lesson, and use only the toolkit output intended for the field you are editing. Editorial cross-reference review: October 30, 2026; native OD workflows remain untested unless an actual outcome is recorded.

All lessons · Glossary · Complete handbook · Open toolkit

Start with one small practice project

Use the original practice character Mira, a 30-year-old adult archivist, or your own original adult character. Rowan, the 32-year-old adult courier, is an optional supporting character. Start a fresh practice chat when a lesson introduces a different premise. Keep temporary scene clothing and lighting separate from stable appearance.

In the toolkit, choose Load Mira example, select a panel, fill the relevant fields, and choose Generate. This assembles text locally. Read each labeled output, then use its Copy button and paste it into the stated website field. Choose Download project to keep a backup; Open project restores that companion backup. Browser draft storage is best-effort.

The companion prepares text, checks supplied drafts, records tests, and maintains a small local RPG ledger. Website sign-in, image and media generation, native configuration, calls, and publishing remain manual. Follow the controls and costs actually shown in your account. A missing native control is a reason to stop that website procedure.

Choose a learning path

Create a first character

Start here if you have never made a character. Create a private practice card before adding optional systems.

Read in order: 01 Getting started → 02 Create your first character → 03 Character sheets → 08 Personality and roleplay engines → 09 Scenarios greetings and worldbuilding → 14 Personas and Custom Instructions → 23 Testing and troubleshooting.

Toolkit panels: Character fields, Roleplay, Consistency check, Test records.

Optional starters: E1. Reference: Framework.

Check before moving on: The private practice character has separate appearance, personality, scenario, and greeting fields, and you have inspected one real reply.

Build a CPD and make art

Begin after creating a character. CPD means Custom Physical Details: the stable visible appearance, rather than a temporary scene description.

Read in order: 04 CPD and Face Details → 05 Art styles → 06 Generate images → 07 Edit images → 18 Gallery and image reuse → 24 Community Presets.

Toolkit panels: CPD, Art prompts, Consistency check, Test records.

Optional starters: E7. Reference: Art, Template.

Check before moving on: A saved prompt identifies its real model and route, and you have compared the requested change separately from identity drift. Editing starts from an accepted in-app image.

Develop roleplay, groups, and supporting cast

Begin with personality and an opening situation. Decide whether one narrator portrays the cast or separate native characters take turns.

Read in order: 08 Personality and roleplay engines → 09 Scenarios greetings and worldbuilding → 26 NPCs and supporting cast → 10 Group chats → 14 Personas and Custom Instructions → 15 Chat controls and slash commands → 16 Text formatting.

Toolkit panels: Roleplay, Groups and NPCs, Consistency check.

Optional starters: E1, E2, E3, E9. Reference: Framework.

Check before moving on: You know who is present, who knows each fact, which decisions belong to the player, and which respondent is selected. Choose native groups or the single-narrator approach explicitly.

Run a small RPG with memory

Begin after learning personality and scenarios. Keep the first ruleset small; add a native tracker or footer only if the game needs it.

Read in order: 11 RPGs → 12 Memory and continuity → 13 State Trackers → 23 Testing and troubleshooting.

Toolkit panels: RPG ledger, Memory checkpoint, State Tracker brief, Test records.

Optional starters: E4, E6, E5, E9. Reference: Framework.

Check before moving on: One completed event changes the intended value once, no-change cases remain unchanged, and a readable checkpoint is sufficient to resume. Inspect native updates separately from the local ledger.

Plan images, video, comics, and audio

Begin after generating and saving a useful image. Video, comic panels, written dialogue, and audio voices use different workflows.

Read in order: 18 Gallery and image reuse → 19 Video generation → 20 Comic Studio → 21 Voices and calls.

Toolkit panels: Media planner, Test records.

Optional starters: E8. Reference: Art.

Check before moving on: The accepted source image and short motion/panel plan are recorded. Use the available website media controls; voice and calls follow their separate lesson.

Review, publish, and share deliberately

Test the private draft first. Choose visibility deliberately and follow the current website submission requirements.

Read in order: 23 Testing and troubleshooting → 22 Publishing and sharing → 25 Account settings and help.

Toolkit panels: Character fields, Consistency check, Test records.

Optional starters: No engine required. Reference: Framework, Evidence.

Check before moving on: You have checked visibility, the actual submission requirements, and the result shown by the website. Imports and Community Presets use their own optional lessons.

For imports, add 17 Import character cards. For reusable image presets, add 24 Community Presets. For group-based games, read 10 Group chats before the RPG path. For character creation before the art or media paths, complete lessons 01 and 02.

All lessons and their connections

The preparation column gives suggested reading, not enforced website dependencies. Numbers are links to lessons. Panel names match the toolkit exactly. E1–E9 link to the plain-text starter files described below; they are optional aids, not a stack to install. Each lesson explains its actual account, source-image, or feature prerequisite.

The Engine library panel contains all nine starters. Consistency check inspects the supplied draft; Test records stores what you actually tried and observed. Neither demonstrates model compliance. For audio and account actions, the relevant lesson is a manual checklist rather than an automated tool.

Choose one starter and its destination

An “engine” here is a compact writing template. Choose one conflict-free behavior base, then add only a needed supporting module. Replace every [replace ...] placeholder, remove unused optional lines, and reconcile existing instructions. Imported source text remains reference data; it does not acquire special authority from a title or code-looking format.

E1: Agency and individual knowledge

Open roleplay-agency.txt. Destination: Extra Details (ED), replacing conflicting narrator rules; or chat Custom Instructions for that chat only.

Replace every [replace ...] placeholder before use. Choose one narrator rule set; do not stack this with contradictory engines. These are behavior goals to inspect, not enforced locks. Audio voice selection is separate.

E2: Single-narrator supporting NPC capsule

Open npc-capsule.txt. Destination: Extra Details (ED) of the one narrator-led character; not an automatic native group respondent.

Replace every [replace ...] placeholder. This is a compact ED record for a narrated ensemble. It neither creates a separate character card nor sends these appearance facts automatically to an image model. Do not paste another person into the main character CPD.

E3: Native group shared setup and optional game ownership

Open group-turn-ownership.txt. Destination: Native group Premise/Private Details where offered; otherwise an ordinary group setup message.

Replace every [replace ...] placeholder. Delete the game-ownership lines for ordinary conversation. Match the group fields actually shown; this is not a scheduler or private channel. Selecting a respondent does not establish fictional presence.

E4: Tiny RPG with a manual resolution handoff

Open tiny-rpg-handoff.txt. Destination: Extra Details (ED) for the RPG scenario; actual numerical results are handed back in ordinary chat.

Replace every [replace ...] placeholder. Use the offline RPG ledger only as an external local resolver, with a manual handoff. Define caps and eligible events in that tool separately. Ordinary dialogue does not require a dice roll.

E5: Manual native State Tracker configuration brief

Open native-tracker-brief.txt. Destination: Manually distribute these notes into the actual native State Tracker controls; do not paste the whole brief as an import.

Replace every [replace ...] placeholder. This is a manual UI brief, not an import schema, hidden checkpoint, or executable rule. If native controls are absent, stop native setup. Keep any behavioral consequence in the relevant story instructions without creating a competing numeric owner.

E6: Readable checkpoint for selected continuing facts

Open memory-checkpoint.txt. Destination: Pinned Memories or a maintained local scene note, according to the actual available memory workflow.

Replace every [replace ...] placeholder. Store facts, not a duplicate full transcript or a competing auto-memory log. Use actual native values where they are the maintained owner. No hidden comments or secrets are required.

E7: Rendering-only edit from an in-app base

Open style-only-edit.txt. Destination: The actual image Edit instruction field with the existing in-app generated image selected.

Replace every [replace ...] placeholder. The selected source image is required; copied prompt text is not the image. This states acceptance goals, not guaranteed preservation. Inspect both original and result. Use a new-image route for a new scene rather than silently reconstructing it here.

E8: Small comic or video planning worksheet

Open media-plan.txt. Destination: Local planning notes, then only the relevant scene/motion text in the actual Comic Studio or video input.

Replace every [replace ...] placeholder. This is a planning worksheet, not a universal wizard input. Copy only the relevant description into the offered field. Generation, calls, stitching, publication, and credit use are manual website actions, not offline toolkit functions.

E9: Optional short footer without extra rewards

Open optional-footer.txt. Destination: Extra Details (ED) for a scenario requiring a footer; or that chat's Custom Instructions. Choose one maintained location.

Replace every [replace ...] placeholder before adapting the output shape. Delete this template for ordinary scenes that do not need a footer. This is a presentation contract to test, not native state storage or a guaranteed model self-repair mechanism.

Optional dialogue-writing rule: Comparison Ban

The Comparison Ban module includes the supplied protocol verbatim, a plain-text copy, placement steps, and four proposed checks. Use it with 08 Personality and roleplay engines, 14 Personas and Custom Instructions, and 23 Testing and troubleshooting.

Its focus is direct observation without comparative flattery. Keep praise conditional, preserve established continuity and individual knowledge, and inspect paraphrases as well as exact clichés. It is an optional writing preference; no native enforcement or measured OD efficacy is claimed.

Four references to keep nearby

• Reliable working framework: Field mapping, character records, agency, groups, continuity, RPGs, imports, and readable formatting.
• Art and CPD workflow: Stable appearance, model and route selection, focused scene prompts, and in-app editing.
• Compact image authoring template: A short writing aid for a field-specific CPD, scene, or edit draft.
• Evidence and limits: Explain the reliability filter and distinguish documented features, editorial choices, observations, and actual tests.

The references are a conservative authoring baseline. Document conformance and local software checks are different from observed OD results. Record the actual route, model, input, settings, output, and failures before treating a change as useful. No template guarantees identity preservation, exact memory, arithmetic inside the chat, or consistent formatting.

Keep these handoffs separate

• Stable appearance and scene: use CPD for durable visible traits and the actual scene prompt for temporary clothes, pose, setting, or lighting.
• One narrator and native groups: a supporting NPC capsule belongs to one narrator's ED. It does not create a separate card or select a native respondent.
• Local RPG and native state: the RPG ledger computes local events. A tracker brief is manually transferred into native controls; a checkpoint is a maintained fact record. Inspect each actual owner.
• Image prompt and image input: an edit requires the accepted in-app source image, not just its copied description. Card import reads a compatible portable card; it is a different workflow.
• Written voice and audio: personality and dialogue examples shape writing. Audio voices and calls use their own available website controls.
• Project and card files: a companion project backup uses ourdream_companion_project version 1. The portable Mira card is an optional importer fixture, not an Open project backup; its OD mapping has not been live-tested.
• Draft and publication: copying a description does not change visibility or submit moderation. Complete 22 Publishing and sharing on the actual website.

Keep a downloaded Mira project example or your own project backup. The plain-text test log is available if you prefer ordinary files. Keep credentials, private chat excerpts, and account details out of anything you intend to share.

October 30 reconsolidation modules

The original sources remain archived. The maintained library now includes these optional, destination-specific modules. Their proposed OD checks remain unrun until actual replies or images are recorded.

• Character motive and written voice / copyable starter: Local worksheet; distribute motives and voice into APD, starting situation into Scenario, and continuing facts into memory.
• Continue a scene without forcing the player / copyable starter: Extra Details (ED), or the current chat Custom Instructions; choose one maintained location.
• Individual knowledge and evidence / copyable starter: Extra Details (ED), or the current chat Custom Instructions; learned facts stay in the maintained scene/checkpoint.
• Complete resume checkpoint worksheet / copyable starter: Local scene notes; review selected continuing facts for Pinned Memories. Keep the separate full companion project backup.
• Comparison Ban: grounded observations / copyable starter: Character APD/ED or chat Custom Instructions as appropriate; choose one maintained behavior location.

Read the source review, source-family register, and verification record for dispositions, coverage, actual software results, and unrun native efficacy tests.

Practice OD prompt writing

Use the OD chat prompt lab after lessons 03, 08, 14, or 23. Rewrite a vague request as observable behavior, choose its field and lifetime, then compare the revision with the saved baseline. The lab includes voice, one-time direction, and text-language exercises plus a local worksheet. Prompting guides a selected model; it does not fine-tune it or identify its provider.

Optional form, tracker and scenario worksheets

Use current-form continuity for changing appearance and accepted image sources, affection tracker review for evidence and bounded state changes, and scenario engineering for premise, access, knowledge and an open launch. These are original teaching adaptations of supplied sources. The worksheets are local plans; native configuration and outcomes require actual controls and recorded trials.

Non-graphic voice, pacing and consent

Use the Known State module and its plain-text guideline with lessons 08, 14 and 23. Open the text file and copy only its response-writing block to the intended chat Custom Instructions scope. Trial Current Chat where offered; record actual replies before judging its effects.