Writers and creators

Goal: Build a story bible that separates established canon from proposed ideas, so your next scene starts with the decisions already made.

When this helps

You return to a serial story after three weeks. The current scene sends Mira overseas, but an earlier character note says she has never left her island. A collaborator has a promising explanation in a chat, yet no one agreed whether it becomes canon. The problem is finding and deciding the reference, rather than producing more disconnected ideas.

Use Story practice as your exercise theme. The same approach works for a novel, a comic, or a video series: connect characters, world rules, plot choices, source research, and tone. Start with one character and one episode instead of documenting the entire world first.

Before you start: Complete your first workspace and select a workspace where you are an Editor or Owner. You can complete this exercise without an AI connection. Markdown is ordinary text with headings, lists, and tables; you do not need to write software code.

Fictional practice material

The examples are invented. When using your own files, check ownership, permissions, and the intended readers before uploading or sharing them.

Separate sources, canon, and proposals

Material	Home	Purpose
Permitted reference photos, research extracts, recorded source links	Library	Preserve the material behind a detail and its provenance.
Character Mira	Context	State established character facts, voice, and unresolved motivations.
Episode outline	Context	Explain the current scene goal, dependencies, and proposed changes.
Story bible	Context hub	Link characters and episodes and summarize approved world and tone decisions.
Channel tone / content calendar	Optional Context pages	Record wording principles and planned publication dates; these are records, not a scheduler.

Use headings Established facts, Proposed changes, and Open decisions consistently. These are labels you write in the page, not an automatic canon-approval mechanism. Keep your personal unpublished brainstorm in saved private editing; once shared or published, explicitly label proposals so readers do not confuse them with settled facts.

In words: the story bible connects research, character facts, and episode choices. A person compares them before accepting a change or revising a scene. The diagram does not imply automatic continuity validation.

Build the connected reference

1. Open Context → New Context page. Put the first page title below in the title field and its Markdown in the body.
2. Choose Save draft and check that saving completes. Read the page, then choose Publish. This makes a workspace version available to readers; it does not enable anonymous web access.
3. Create and publish the second supporting page the same way.
4. Create the hub page last. Type [[ or choose Wikilink to select each existing target. The copied [[Page title]] text is a starting point; select the correct page if a title is ambiguous.
5. Publish the hub and open every link in the reader. Check the workspace and actual target if a link does not resolve.

For toolbar, citation, and editing details, see Context pages and images and links.

Copy the page content

Create the pages in this order. Put each heading’s page title in the title field and paste the block below it into the body.

Character Mira

# Character Mira

## Established facts
- Mira repairs clocks in a harbor town.
- She has never left the island.
- She keeps a notebook of unusual sounds.

## Voice
Short, practical sentences.

## Not yet decided
Why she refuses to repair the lighthouse clock.

Episode outline

# Episode outline

## Opening
Mira hears the lighthouse clock ring at midnight.

## Scene goal
Introduce the mystery without explaining its cause.

## Continuity check
Mira can describe local streets but not a personal trip abroad.

## Open choice
Who else heard the bell?

Story bible

# Story bible

## Working title
The Midnight Clock

## Characters
[[Character Mira]]

## Current episode
[[Episode outline]]

## Established world
A small island town; the lighthouse is closed.

## Tone
Quiet mystery, concrete sensory details.

## Open decisions
The cause of the midnight bell remains undecided.

Use the reference while drafting

1. Open Search, enter Story bible, and choose Scope → Context. Open the hub and follow the link to Character Mira before drafting a scene in her voice.
2. Read Established facts and Not yet decided. Mira has never left the island; her reason for avoiding the lighthouse remains open. Only the first is a settled constraint in this exercise.
3. In Episode outline → Edit, add Proposed scene: Mira recalls a trip abroad and state the conflict with the character page. Choose Save draft while you consider it. Saving does not silently change the published story reference.
4. Decide between two concrete choices: change the memory to a local event, or approve a deliberate change to her history. If you change canon, record the reason and affected episodes rather than quietly replacing a sentence.
5. Update the character page and outline together as needed, publish the accepted revisions, and reopen both reader-facing pages. Use History to compare the old statement with the new decision.

If a collaborator has already changed a page, inspect View their changes before overwriting it. Preserve mine as alternative, when offered, keeps your work; it does not merge the story or decide which version is canon. See Context pages.

Keep worldbuilding and research usable

For the next episode, add an optional World — Harbor town page with geography, clock rules, and unresolved mysteries, then select it through the editor's Wikilink command from Story bible. Place “The lighthouse is closed” under approved world facts; place “The bell is caused by a tidal mechanism” under a proposal until you decide.

Upload permitted research to Library → Upload, then inspect the item and its processing status. Read the relevant original passage before citing it in a Context note. Image storage does not provide automatic OCR, and an image's presence does not establish reuse rights. For a scanned historical source, add your checked text summary if extraction is unavailable.

Use the editor's Citation control next to a supported detail and select the real source. Distinguish a historical observation from your fictional adaptation: “Research describes this mechanism; the story uses a different timing.” Preserve source credit and avoid passing someone else's illustration off as original work.

Carry the same tone into the next channel

A creator can add Channel voice with audience, tone, preferred terms, and words to avoid. Link it from Story bible. Include one approved sample caption and a clearly marked alternative; “Short, practical sentences” can guide Mira's dialogue, but a channel announcement may need a different audience and wording.

For a content series, a Content calendar page can record episode, planned date, status, and the link to its outline. Update it yourself after publishing through your normal channel. dtxWiki does not schedule social posts, upload videos, or confirm that an episode was distributed.

At the end of a writing session, add one line to Open decisions for any unresolved change. Before starting the next session, search the hub, check the relevant published facts, and close decisions you have actually made. This keeps a useful small reference instead of an ever-growing list of unclassified ideas.

Review and share the intended material

A co-author needs workspace membership and a suitable role. Use Share → Copy workspace link and check their access. Browser Save draft is saved editing, not explicit Review submission. If an integration submitted a change, open Review queue → Pending, inspect View changes, and request a specific correction or approve when eligible. Otherwise, agree the editorial decision and have an Editor or Owner publish it directly.

For a reader-facing world guide, create a separate summary containing only approved spoiler-safe material and permitted media. Preview its published version before web exposure, then check the anonymous URL signed out. Do not publish the internal story bible merely to share one character description; linked drafts, research rights, and spoilers need their own check. See sharing.

Check the result

• You can reach the character and episode from the hub without finding an old chat.
• A collaborator can point to what is canon, proposed, and still undecided.
• The “trip abroad” conflict has an explicit decision and corresponding published edits.
• Sources and adaptation notes remain distinct; History explains deliberate retcons.
• Channel tone and planned dates, if used, are readable records with a responsible person.

Optional: use AI as a comparison partner

Complete MCP connections first and grant only the required workspace and reading permission. These prompts request no writes. The credential grants and workspace permissions control access; wording in a prompt does not enforce them. An external AI service can receive material its tools read, so use only material you may send to that service.

Read Story bible, Character Mira, and Episode outline. Compare the proposed scene where Mira remembers travelling abroad with established facts. Cite brief supporting passages, list unresolved choices, and suggest two ways a writer could resolve the conflict. Do not decide canon or edit the story. Reply here only.

For a creator's additional pages:

Read Channel voice and the current Episode outline, if those pages exist. Propose two short announcement captions in the recorded tone, avoiding spoilers listed in the outline. Separate supported details from assumptions. Do not invent missing pages, schedule a post, or change the calendar.

Open the cited pages yourself and check both the contradiction and each proposed solution. AI can miss conflicts, introduce new lore, or flatten a character's voice. You choose which idea belongs in the work, then record and publish the decision.

Chats records dtxWiki tool activity; it is not the complete conversation or a record of every external action. None of these examples depends on an AI service.