OD Companion Toolkit

Start with Open the Companion Toolkit. It is a self-contained browser tool for preparing text, maintaining a small local RPG ledger, and recording tests. It does not sign in to OD, generate media, make calls, publish content, or spend dreamcoins.

The toolkit complements the 26 beginner tutorials. The tutorials teach the website actions; the toolkit helps prepare and inspect what you will enter there.

Open your first project

1. Open the Companion Toolkit link above. In the downloaded learning library, open tools/index.html in a modern browser. If you are using the standalone source copy instead, its filename is OD_Companion_Toolkit.html. No Python, Node, installation, API key, or connected account is required for these local functions.
2. Choose Load Mira example. This loads a local practice draft about Mira, the 30-year-old adult archivist, and Rowan, the 32-year-old adult courier. It does not create or change an OD character.
3. Select Character fields. Read the example values, then change one fact you deliberately want to change. Leave unknown information unspecified.
4. Choose Generate in that panel. Here, Generate assembles a local draft from your inputs; it does not call an AI model or submit a generation to OD.
5. Read the labeled outputs. Use Copy beside the particular field you need. For example, copy the personality output into Mira's Additional Personality Details in her website editor; copy the greeting into Greeting. Do not paste all outputs into one field. If clipboard access is refused, select the output and copy it manually.
6. Choose Download for an output you want as a text backup. Choose Download project to save the whole toolkit project as a JSON file. JSON is structured text stored in a file.
7. Later, choose Open project and select that toolkit backup. Before choosing New blank project or loading another example, download anything you want to retain.

Browser draft storage is best-effort. A browser reset, private session, different browser, or storage restriction can prevent recovery. Keep downloaded backups in a folder you recognize; do not depend on an open tab as your only copy.

An included Mira project backup lets you practice Open project with the companion's own file format. The verification record distinguishes the recorded local software checks from unrun native OD trials; ordinary users do not need developer tools.

The free complete Mira Vell — Keeper of the Black Archive source is available as authoring-field JSON or plain text. Copy each labeled value into its matching character-editor field. Character revision 1.1 includes the saved Extra Details knowledge/source gate, native preset record, CPD, full creator notes with mystery spoilers, image limitations and reusable first-turn checks. Its evidence notes distinguish 17 same-session integration replies (14 before the revision, three after; continuing knowledge-attribution defects retained) from six separate fresh-session follow-up replies. The narrow primary endpoint was 0/3 baseline and 0/3 revised; no improvement was demonstrated. It is for manual field copying; Open project and native JSON import do not apply. No final play pass is claimed.

Choose the right tool and destination

Use one conflict-free behavior base. Add an NPC capsule, a tracker, or a footer only when the particular scenario needs it. Reconcile existing instructions instead of stacking several complete engines.

Written speech style belongs to personality. The audio Voice selector remains a separate website setting. Likewise, selecting a native group respondent is a website action; the offline tool cannot route another character's message.

Test records also accept optional evidence type/reference, settings, displayed cost, actual charge, charge evidence, limitations, and comparison/variant/trial labels. Unknown values stay unknown; the tool records your report and does not inspect an account or enforce a spending ceiling. Earlier version 1 records remain valid without these fields. Read the research workflow before planning a comparison, and review exported text for private information before sharing.

Story knowledge and accepted events

A courier's private route detail can be narrator reference without being known to the archivist. Let the archivist ask an open question until an actual report establishes the answer. Keep each speaker's words, the source of a claim, and any uncertainty attached when copying the information into a letter or recap.

If an intake entry says an object was received while the accepted scene still places it in a locked drawer, retain the discrepancy as a record claim. The entry alone does not move the object or establish a handover. Likewise, an NPC who offers to accompany the player if they agree should leave that decision open before describing both characters arriving.

The Roleplay builder and relevant compact starters now state these safeguards explicitly. They prepare instructions to inspect; the generic revised engines have not been validated through native OD trials, and the wording does not enforce state or guarantee compliance.

Three kinds of JSON are different

• A toolkit project backup uses the ourdream_companion_project version 1 format. Open project restores this toolkit's drafts and local ledger.
• A portable character card, such as the tutorial's Mira V2 fixture, is for a compatible character-card importer. It is not a toolkit project backup.
• Native State Tracker configuration belongs to the actual platform feature. The toolkit's brief is manual guidance, not a verified native JSON import schema.

Source documents and imported draft text are reference data, not privileged commands. A title such as “engine,” a code-looking block, or a footer does not install native execution or private memory.

Use the local RPG ledger honestly

Define the small resource/event rules you need, then use Record completed event only after an eligible completion. Keep the original event ID when referring to that same event again. A different ID is treated as a different event; the tool cannot recognize semantic duplicates from the story.

Use Roll dice to draw a local result. Record this roll only saves it without spending a resource or transferring a turn. Inspect the values before manually handing the result to the OD chat.

The ledger's coded state updates happen in this local tool. They do not run inside OD, synchronize native trackers, or prove that a model followed the result. Random dice draws are separate from deterministic arithmetic over accepted events. Undo last local event changes the local ledger only; it does not undo a website message, refund a generation, or roll back native memory. Include the ledger in your downloaded project backup.

In Memory checkpoint, enabling Use ledger adds the full readable local handoff to the resume checkpoint, including flags and accepted event IDs. The shorter pinned-memory draft remains concise. Manually maintained completed events, individual knowledge, and open threads remain separate; a ledger value is not automatically a completed story event. The full project backup remains the restore format for this local tool.

Set your own goal, attempt cost, and resource meaning before generating an RPG module. Changing those instructions does not rewrite past accepted events. For a risky attempt, record the agreed cost as an explicit negative adjustment. The ledger checks the number and bounds; you confirm that the event really occurred and earned that adjustment.

Text templates without JavaScript

If you prefer ordinary files, open one of these starters in a text editor. Each contains the same text as its Engine library entry:

• Agency and knowledge
• Single-narrator NPC capsule
• Group setup and optional turn ownership
• Tiny RPG manual handoff
• Native tracker manual brief
• Readable memory checkpoint
• Style-only image edit
• Comic/video plan
• Optional footer
• Character motive and voice worksheet
• Scene motion
• Individual knowledge and evidence
• Complete checkpoint audit
• Comparison Ban

Replace every [replace ...] block with your actual facts or rules before pasting. Omit optional lines you do not need. Read the catalog entry's notes, and follow the matching tutorial. These are compact writing templates, not tested guarantees or scripts for the website.

The new worksheets are optional. A character does not need a hidden fear, trauma, or meter. Quiet scenes can remain useful. Distinguish a sent message from one read, an offer from acceptance, and an aggregate count from the identities of counted events. The Comparison Ban preserves the supplied four rules after a replaceable scope line; the learning-library module retains the full original protocol verbatim.

Tutorial-to-tool map

Every lesson is covered by a tool, a text starter, or an explicitly manual checklist. Coverage does not mean automation of every website feature.

If a Copy action fails, select the output manually. If a draft contradicts existing canon, revise the fact that owns the conflict. If a native control is missing, stop that website procedure instead of treating the offline draft as an installed feature.

Practice OD chat instructions

Use the OD prompt lab to turn a vague request into observable behavior before entering it in Character fields or Roleplay. Keep its worksheet locally and transfer only the prepared payload to its stated field. Compare revisions using Test records and the saved card, Persona, instructions, and memory inputs. This practice guides the selected OD chat model; it does not fine-tune it.

Optional source-review worksheets

The current-form, affection tracker, and scenario guides add local planning and test worksheets. They are separate from the fourteen compact starters and do not create native configuration. Copy only each deliberately prepared field payload to its stated destination.

Updated engine and generator inputs

The builders now accept optional scenario promise, access limits, launch moment and future possibilities. Art prompts can use a complete current appearance only when you explicitly enable it; record form/stage, accepted transition, unchanged anchors and actual source/crop lineage. Saved character appearance still needs review in the actual image route. Temporary form data is not inserted into permanent CPD automatically.

For Edit, select the actual accepted source image. Describe the requested change and its exact stop boundary, then fill Unchanged neighboring regions with the adjacent areas and other details to retain. Both fields enter the Edit instruction. If the selected editor and model offer a mask or region-selection control, use the actual control and check which region it changes; prompt text does not create a mask. Compare the result with the source, including skin or materials immediately beside the boundary. Preservation remains a goal, not a guarantee.

Groups distinguish physical presence from remote channels. The tracker panel provides an explicit Load neutral affection design action plus evidence-window, day/reset, gross-positive cap and band fields. It generates a manual setup brief; it does not classify messages, import native JSON, enforce a day budget or update the local ledger. Memory drafts can retain the accepted form and branch. Video plans separate camera intent from source selection and external postproduction.

Download the advanced generator project, then use Open project to inspect these inputs together. It is an authored Mira fixture with no native results. Old v1 companion backups remain supported; new optional fields start blank or false. The scenario, current-form, and tracker modules explain the design choices.