XR platform family / Content production
XR Content Platform
Interactive XR content becomes repeatable only when the production logic survives beyond a single episode.
This record covers the content-production direction within the XR platform family: structured episode data, media processing, interaction logic and publishing. It remains separate from XR Conversation Simulator until a shared core, repository and deployment boundary are verified.
- Status
- Active
- Evidence
- Documented
- Ownership
- To confirm
01 / The operating problem
Interactive episodes break apart when every role works from a different version.
XR production combines scripts, learning parameters, source media, video processing, interaction logic and feedback. The source positions XR Content Platform as the shared environment that keeps those parts connected. It supports the production workflow; it does not replace the creative, educational or technical decisions made by each team.
Participants
A shared production layer linking episode structure, media, interaction logic, feedback and user-response data.
System outcomes
Connected modules
- 01Scenario model
Structures scripts, parameters and episode content.
- 02Media pipeline
Processes and prepares 360-degree video.
- 03Interaction layer
Defines branches, user actions and feedback.
- 04Response analytics
Returns documented user-response data to the team.
02 / What stays shared
The reusable value is a production model that content teams can configure.
The local source defines one content workflow and names MUSEIS and NaviXR as related product contexts elsewhere in the repository. That establishes a reuse direction, but it does not prove that both products currently run on one deployed shared core.
Shared core
Episode, media, interaction and response model
The documented foundation joins the main objects and handoffs in XR content production.- Scenario and episode structure
- Content versions
- Media processing
- Interaction logic
Configured layer
The rules of each experience
Learning parameters, content structure, branches, feedback and delivery conditions vary by use case.- Learning parameters
- Episode structure
- Branch logic
- Feedback behavior
Connected environment
Source media and delivery clients
A deployment must connect storage, video processing and the devices or clients that consume published content.- 360-degree source media
- Storage and transcoding
- Web or XR client
- Analytics destination
Implementation work
Workflow, infrastructure and governance
Teams still need to define permissions, approvals, media infrastructure and content operations.- Role and approval model
- Media infrastructure
- Device profile
- Content governance
03 / What the platform enables
Capabilities follow an episode from scenario to response.
- StructureScenario and episode creationContent creator
Scripts, learning parameters and content structure share one episode record.
documented - ContentCentral content managementProduction team
Participants can work from the latest documented content version.
documented - Media360-degree video processingMedia producer
Source video can be prepared for different formats, devices and bandwidth conditions.
documented - InteractionBranching and feedback designExperience designer
User actions, branches and feedback can be attached to the episode.
documented - LearningUser-response analyticsEducator or content lead
Response data can inform review of content quality and effectiveness.
documented
04 / How it connects
The platform sits between source content and the experience that consumes it.
Inbound
- Scripts and learning parametersThe source names both as inputs to scenario and episode creation.confirmed
- 360-degree source videoVideo processing and optimization are part of the documented capability set.confirmed
Platform responsibility
- Episode and content structure
- Versioned production context
- Media processing
- Interaction and branch logic
- Feedback definition
Outbound
- Device-ready XR contentMultiple formats and devices are named, but exact delivery clients and format coverage are not specified.implementation-specific
- User-response dataAnalytics are documented, while events, storage and reporting interfaces still need definition.implementation-specific
05 / How it enters use
The first deployment should prove one complete episode workflow.
- 01Model
Define one episode, its content objects, roles and learning parameters.
- 02Configure
Set the production workflow, branches, feedback and approval boundary.
- 03Connect
Connect source media, processing, storage and one delivery client.
- 04Validate
Publish and review one episode across the intended target conditions.
- 05Operate
Assign content ownership, analytics review, versioning and support.
Laravel, Laravel Nova, Vue 3 and Inertia are named in the source. The current material does not define hosting, media-storage architecture, transcoding services, supported clients, tenancy, security review or service terms. Those choices belong in implementation scoping, not in a generic promise.
06 / What is verified
The production model is documented. Working reuse still needs verification.
End-to-end content workflow
The source connects scenario creation, content management, 360-degree video processing, interaction design and response analytics.
- Source
- platforms-v2.md
- Limit
- It does not identify a current running environment, throughput or operational owner.
Multi-role production setting
Content creators, educators and production teams are named as participants in one shared process.
- Source
- platforms-v2.md
- Limit
- Permissions, approvals and handoff behavior are not specified in the source.
Related product direction
MUSEIS and NaviXR point to XR Content Platform as an enabling platform in the local project records.
- Source
- MUSEIS and NaviXR project frontmatter
- Limit
- The relationship does not prove that both products run on a shared deployed environment.
Ownership and access
How the platform enters a real engagement
- OwnershipopenTo confirm
The current source does not define platform ownership or the boundary of reusable intellectual property.
- First engagementdefinedOne episode discovery
The first useful scope is one content team, one episode, one delivery client and a reviewable publishing workflow.
- Commercial and service modelimplementation-specificImplementation-specific
Licensing, media infrastructure, implementation, hosting, support and pricing remain open.
Next step
Bring one episode and the team that owns it.
The right first conversation connects content, education and production around a single reviewable workflow. It should also resolve how XR Content Platform relates to the separate XR Conversation Simulator.
Start a platform conversationXR Content Platform is presented at a documented evidence level. Ownership, working modules, shared reuse, delivery clients, media infrastructure, analytics, hosting, support and commercial terms require confirmation.