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 the account-owned character library with its creation form ready. You can develop that reusable character before attaching it to a Story cast; no Story selection is required to create it.

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.

Each Story in the Stories list shows its completeness with its blocking-error and warning counts. When Studio can name the next fix, the Story offers it as a link that opens the area to correct. The sticky header names the open World, Story and Episode. Use any linked name to open its overview. Documentary, instructional and World-less Stories show their Story alone. Global pages and the independent Character library have no content hierarchy. Use the sidebar to open collections and tools; it keeps the full Worlds and All Stories lists available.

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 library stores account-owned, reusable character profiles. You can create a character without choosing a Story, then develop its identity, goals, voice, relationships, boundaries, portraits, and other profile details in Characters. Story-specific schedules remain Story content. Select an attached Story in the Character workspace's Story cast selector to manage its goals, secret conditions, relationships and event bindings; the Story itself exposes attachment, removal and scene participation instead of another character editor. Attach an eligible library character to a Story when it belongs in that cast; the Story keeps a cast binding to the library identity instead of creating a second character owner. Remembered encounters and evolving relationships use the published Story and World continuity when readers meet that character. Character goals use structured text, priority, and timeframe, and runtime character behavior reads the authored profile. Published character and location snapshots are immutable, while later edits remain available for a future publication. Locations and the World map describe where Story events can occur. Required fields and ownership checks are enforced when saving; another creator's character or location cannot be edited through your account.

Removing a Character from a Story detaches that use and leaves the reusable Character and its artwork intact. Remove reported event or branch references before detaching. Deleting the reusable Character is a separate action in Characters and is refused while Story attachments, publications, media or usage obligations still require it; archive remains available where those obligations prevent deletion.

Review AI tool proposals

Open a Story's AI Tools workspace to request an outline, rewrite, extraction, continuity check, cinematic cues, schedule, or tension adjustment. Choose the Story, character, location, or event context offered by that tool, supply its requested inputs, and review the provider and cost information before generating.

A generated proposal is a candidate for your draft. Review its structured changes and select the items to apply, or use the available apply-all action after reviewing the whole proposal. Discard a candidate you do not want, or adjust the instructions and request another. Applying changes saves draft content; publication remains separate. The run history lets you reopen a saved proposal or export its JSON. Reopening or exporting a run does not apply it again. Read the result and any refusal before moving to another tool; a failed action does not establish that the requested change was saved.

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

Use the Publish rocket in the Story header to open the shared publishing flow. For fiction, choose an episode. For an Instructional, Publish opens directly for the complete saved instructional. Follow Summary → Lint → Diff → Changelog → Confirm in the same publishing wizard. Instructional review covers all saved curriculum, lesson content, evidence, practice and assessments. Explicit confirmation freezes that complete curriculum into a new version; earlier published versions remain immutable.

Course sections retain unsaved curriculum edits while you move between them. Opening Publish or History saves a dirty curriculum before leaving the editor; a failed or stale save keeps you there with the reason. History opens the shared release history. After a successful publication, the shared Production queue shows progress, failures and retry. Use its release links to inspect History or preview that exact published version.

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. Fiction retains its character, location, event, branch, timeline and episode references within that version; an instructional retains its complete curriculum and references. 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.

Screen saved episodes

Open Preview and choose a saved draft or a Ready publication, then select an episode. Use Start at to begin at its opening or a saved event. At an authored choice, select what happens next; the player follows that path and leaves the other ending out.

In Structure → Events, Screen saved from this event starts at the selected saved event. Versions can screen the selected source or begin at a changed event in its comparison. Save your edits before screening them. Interactive preview opens the separate playable sandbox.

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.

In Structure → Events, open an event and use Add Ad Break after a complete beat. Move or remove that placement with its adjacent controls. The final beat of a Story-ending event cannot carry an ad break. Published placements are read-only; a copied or imported Story needs its own saved advertising approval.

Episode screening can show a clearly labelled local sample, a Premium skip or a no-fill continuation at an authored boundary. Each returns to the next authored beat. These screening choices make no ad-network request and create no impression or financial record.

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. Generation runs as an import job; Quick Story follows that job's status, reconnects if the status check is interrupted, and reports whether the job completed or failed.

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.

Authoring a course

Choose the instructional format when creating the Story. Its workspace keeps curriculum, lessons, practice and evidence together as you move between sections. Save the whole curriculum when its required fields are complete. Use the header Publish action to enter the same five-step publishing wizard used by Stories for the complete saved instructional.

For a narrated presentation, add lesson scenes and choose approved presenters from your Character library. Author and review each scene script, then lock it and use Publish reviewed scripts before producing its scene media. The scene duration is a timing plan; Prepare narration measures the retained voice performance. Review that measured result and the intended quiet actions before settling the final timing.

Add approved images or upload genuine screenshots, compose their Stage placement and finite Motion, and place sound effects and ambience at their actual beats. The sound picker can generate a sound, preview it and use the retained result in the selected scene. Rehearse plays the saved lesson presentation so you can review its acting, readable visuals and sound.

Run validation and the release check, use the finding's Quick fix or Quick fix all, and review the verified result. A Quick fix saves its repair and reruns its check. Review the complete instructional in the shared publishing wizard, confirm its release, then follow Production and review the public course on desktop and a narrow screen. Playback position and assessment mastery remain separate for your audience.