World and Experience Studio

Purpose

Translate governed canon into emotionally coherent interactive and cross-media experiences without allowing product production to overwrite world authority.

When it fires

• Building an Arcanea or other owned-world game, cinematic site, interactive story, visual bible, soundtrack experience or collector edition.
• Combining narrative, software, visual, motion, music and physical/digital artifacts into one experience.
• Resolving canon drift or compiling world material for web, app, book, music, itch.io or collector channels.

Inputs

• Product manifest, exact canon authority revision, conflict/migration ledger and World and Experience Studio task envelope.
• Audience journey, experience brief, platform targets, rights record, asset registry, design pack, budget and target channels.

Workflow

1. Resolve artifact class, canonical world repository, product repository, Studio pack and channel adapters. Keyword or thematic similarity never grants canon ownership.
2. Classify proposed material as canonical, proposed, variant, historical, superseded, licensed or non-canonical. Preserve valuable contradictions in a migration ledger rather than deleting them silently.
3. Bind the emotional journey, interaction loop, medium responsibilities, accessibility/performance budgets, state/save/version model and release stop conditions.
4. Assign canon architecture, experience direction, systems build, cross-media production and independent verification to distinct owners. One manager synthesizes.
5. Produce bounded sub-envelopes for Publishing, Software, Media or Template Studio contributions. Require stable IDs, exact revisions and evidence on return.
6. Integrate text, visual, motion, sound and interaction against the same canon and design revisions. Verify mobile, reduced motion, audio control, captions, loading, recovery, save/state and static fallback.
7. Compile channel packages for web, app stores, books, music, itch.io or collector delivery without redefining canon, product rights or commercial terms.
8. Issue a release receipt containing canon delta, cross-media versions, runtime evidence, rights, spend, accessibility/performance results, long-term access and rollback/takedown routes.

Output contract

Return canon classification and delta, conflict ledger, experience architecture, integrated build or package, cross-studio receipts, channel packages, verification evidence, release receipt and release decision.

Tools and MCP

Use GitHub for canon, product source and receipts; the recorded Arcanea repositories for world authority; starlight-design-intelligence for design and continuity; Figma/Canva for deterministic assets; Remotion/HyperFrames for motion; Vercel for web previews; and Drive for private masters and evidence.

Quality bar

• Canon authority and product authority are distinct and explicit.
• The experience has one emotional and interaction thesis across every medium.
• Cross-studio contributions are bounded, versioned and evidence-bearing.
• Mobile, accessibility, reduced motion, audio control, performance, save/state and fallback paths pass where applicable.
• Collector mechanics create durable experiential value; NFT use defaults to legal, rights and security hold.

Built on SIP — Starlight Intelligence Protocol Vertical: federated-product-studios · portable capability layer