Mystrix Studio authoring

Worlds, stories, and drafts

The Creator introduction offers three equal starting points: build a world, shape a playable story,

or create a living character. Choose the part you know first; this choice does not publish anything

or lock you into a required authoring order. Starting with a character opens a story chooser because

characters are story-scoped. Select an existing story to open its character creator, or create the

story draft first when no story exists yet.

Mystrix Studio keeps authoring work in drafts until you publish a valid story version. Worlds hold

shared setting and canon information; stories contain the reader-facing narrative built in that

world. Use the Worlds and Stories lists to create, open, duplicate, and organize work you own. A

draft is not visible through public reader discovery.

Creating a world requires its canonical content rating, normalized blocked-topic list, and all four

safety-profile levels. Those values are publication inputs, not defaults the server invents for a

partially configured world. A world can also reference up to eight representative image assets;

each must be an image you own that has not been rejected. Duplicating a world copies its authored

setting and representative images, but the copy receives a new encounter-policy master control.

Template basics

A world template is a reusable starting point, not a published world. Give it a name and useful

description, choose a category and search tags that describe the intended use, and keep it private

until it is ready for other creators to discover. Genre and tone fields guide the worlds created

from it; they do not replace the creator's later review. Creating or updating a template saves only

the supported authored fields, and using one creates a separate editable world.

Template canon and facts

Canon rules state constraints that should remain true in a world made from the template. Global

facts are structured key/value references for setting information. Prefer a small number of clear,

non-conflicting entries over repeating the description. Review both lists before making a template

public: a creator can edit the new world later, but the template should begin with internally

consistent guidance.

Template safety and content rating

Choose the content-rating tier that matches the material the template is designed to support, list

blocked topics explicitly, and set each safety-profile level intentionally. These fields travel

into worlds created from the template and are publication inputs; they are not decorative tags.

Use stricter limits when the template's premise is suitable only if particular material is kept

off-page, and recheck the resulting world before publishing a story from it.

Page content structure and media

Creator content posts have a title, optional description, and one selected content type. Keep the

type consistent with the post you intend to publish, use the local media preview to inspect a file

before submission, and keep the text understandable when media is unavailable. Creating a post

does not change a story draft or publish a story version; it creates a separate creator update.

Page visibility and scheduling

Save unfinished page content as a draft. Choose publish-now only after reviewing the title,

description, content type, and media; choose scheduled only with an intentional date and time.

Editing a published or scheduled post changes that post's current status, so recheck the selection

before saving. A schedule is not a story publication and does not bypass content or media checks.

Go-live confirmation

Before starting a live broadcast, confirm its required title, optional description, and the camera

and microphone preview state shown in Studio. “Schedule” creates a scheduled stream record, while

“Go Live” creates and immediately starts one. Going live is an external-facing action, so use the

local preview controls for device testing and review the setup again before confirming.

Characters and locations

The character editor stores the cast for the story draft. You can create, edit, duplicate, order,

and remove draft characters. A character's identity, goals, voice, relationships, boundaries, and

schedule are authored in that story; remembered encounters and evolving relationships use the same

story/world continuity when readers meet the published character. Character goals use structured

text, priority, and timeframe; saving them also updates the goals used by runtime character

behavior. Published character and location snapshots are immutable, while later edits remain in the

draft for a future version. Locations and the world map describe where story events can occur.

Required fields and ownership checks are enforced when saving; a character or location from another

creator's work cannot be edited through your story.

A character cannot be deleted while a draft timeline event or branch still references it. Open the

reported story items, remove or replace those references, and retry the deletion. Once deletion is

safe, Studio also removes that draft character's owned goal, voice, schedule, and encounter-profile

records and removes relationships to it from the remaining draft cast.

Timelines and branches

A timeline contains ordered events. Branch points connect authored alternatives to that timeline,

and the validation action checks whether a branch is structurally usable. Fix validation findings

before publishing. Deleting an event or branch can affect later links, so review the timeline after

structural edits rather than assuming every connection was rewritten.

Typed canon rules

Open a story's Rules page to create deterministic hard-canon, tone, boundary, canon-fact,

character, and gameplay rules. Each rule has private enforcement text, a scope, priority,

block/warn/guide behavior, and optional machine fields such as banned concepts and allowed

alternatives. Choose whether the rule remains blocking or becomes bendable in Remix Mode.

Private titles, enforcement text, concepts, flags, scope ids, and alternatives never become

reader copy. To show a rule on discovery, story detail, or the in-session World Guide, turn on

its public projection and write a separate spoiler-safe public title and explanation. A signature

rule must have that public projection. Use “Preview public rules” to inspect exactly what readers

can receive.

“Break your world” generates bounded probes from the saved world boundaries and rule concepts,

then runs the same deterministic drift checker used during play. It does not start a session, call

an AI provider, or consume any AI allocation. Save or cancel the open editor before previewing or testing, and

republish after changing rules so a new immutable story version receives them.

Import a story

Story Import uses an owned import draft. Save the draft, prepare its season data, start the import,

and use the job status to see whether processing completed or failed. Import does not publish the

result automatically. Open the created story in Studio, review the imported cast and structure,

then run the ordinary validation and publish flow.

Validate and publish

Publishing runs the story lint and publish guards shown in Studio. Blocking findings must be fixed;

warnings should be reviewed in context. A successful publish creates the reader-visible version

as an immutable snapshot with its internal character, location, event, branch, timeline, and episode

references kept within that version. Later draft edits do not alter the version already being read.

If publish is blocked, use the finding's named section and field to correct the draft. Contact support

with the story id and exact finding when the editor and validation result disagree.

Typed rules outside the current schema also block publication as a whole. Studio does not partially

repair or reinterpret a selector-bearing or malformed rule; open the named rule, correct it, and

rerun validation.

Story advertising in the mobile Creator app

Open a Story's Overview page to choose whether that Story may carry ads. If you opt in, you can

exclude specific ad categories and save the complete policy. The app shows whether the current ad

provider can enforce each category choice. When a category cannot be filtered, excluding it pauses

ad demand for that Story. Turning ads off clears its category exclusions.

The Analytics page shows a recent 30-day advertising report for your own Stories, including

request and fill counts and allocated liability. Detailed reasons are withheld when the audience

count is below the privacy threshold. The report is an accounting view; it does not change your

Story's policy.

Quick Story setup

Open New Story on the Stories shelf and choose the generated path to open a Quick Story

draft. The other choice starts a Story from scratch in the same creation entry.

Quick Story begins by choosing what the import will create. In Story mode, open the program profile

and select Fiction or Hybrid to reveal the World selector. Choose an authorized destination World,

or choose the explicit starter-World option to create and attach a fresh World

when the import runs. That explicit choice remains available when your account already owns a

World; leaving the destination unselected never creates one, even when the account has no Worlds.

It does not silently reuse or replace an existing destination. Episode and season modes

need an owned story series; world mode creates a new world. Story and world titles must be at least three characters.

Destination lists include every world or story you may use, even when the account has more than

one page of results. Story setup also requires one exact

program profile: its form, truth authority, genre, tone, subject, and interaction model must agree.

The profile determines whether the outline contains fiction scenes, documentary evidence

sequences, explainer sections and citations, or an explicitly disclosed hybrid. For a story, also

choose its current content tier: Everyone, Teen, Mature, or Adult. Quick Story carries that exact

choice into the generated Story. When the import creates a World—either in world mode or through

the starter-World path—it applies the same tier to that new World; selecting an existing World

does not rewrite that World's tier. Quick Story does not translate another rating vocabulary or

infer a different tier from the premise.

Quick Story content

For a story, enter a premise to generate a profile-native outline; raw JSON remains an expert import

tool. Documentary generation does not invent characters, choices, dramatic plot turns, or a

fiction ending. You can also paste JSON or upload a UTF-8 JSON/text file using the template offered

for the selected creation target. World, story, episode, and season inputs have different fields;

copy the live template instead of guessing property names. Premise generation produces only the

current canonical story-plot contract; it does not convert older plot versions. The complete draft has one 13 MiB

aggregate content budget, measured again by the server before every write. Quick Story stores this

work in an owned import draft—it has not changed or published the destination yet.

In expert fiction JSON, an event can optionally route completion with one forward,

chapter-local `leads_to_event_index`, or with a non-empty `next_event_routes` array. Every route

contains exactly `required_flags`, `blocked_flags`, and `leads_to_event_index`; the two outbound

forms cannot be combined. Targets must point forward within the chapter, conditions and flags

must be unique, and the active post-completion flags must make exactly one conditional row match.

Malformed, ambiguous, backward, or self-routing input is rejected rather than repaired.

Quick Story review

Before starting the import, confirm the selected mode, destination, title, and whether the expected

data is present. Episode and season JSON may include new characters and locations, so review those

as part of the import rather than assuming only episode prose will change. Starting the import can

create draft material, but it does not publish it. Open the result in Studio, inspect the generated

structure and safety fields, then use the normal validation and publication workflow.