Internal game release
All game development, adaptation and delivery is internal to VORIVOX. There is no external developer portal.
Ownership
A game uses origin_type=vorivox, or acquired for content purchased and adapted by the company. This is provenance, not a role or access boundary. Version creation, uploads, approval and publication require central_admin with central scope.
Sequence
Create game → create version → upload ZIP → resolve validation findings → internal QA → submit → approve → publish. States are draft → submitted → approved → published. Importing a canonical .vxgame is a separate workflow, not a validation bypass.
Cloud
Cloud builds metadata and validates structure, offline policy and runtime; publishing signs and freezes the release. Runtime validation requires an isolated worker without database or signing-key access. A documented API does not eliminate deployment-specific worker acceptance.
Delivery
Publication does not automatically grant launch rights: a separate game entitlement is required. The SDK contains no external self-publishing feature or administrative credentials.