What we publish
Email-verified users can become developers and upload game ZIPs that run directly in modern browsers. Every release becomes its own version: D1 stores catalogue and version facts, while R2 keeps immutable runtime files.
How a game enters the library
For every version, the developer explicitly selects publication languages and provides the matching catalogue copy; the current version’s settings become editable defaults for the next release. If the active version is not published in a language, the game does not appear in that language’s lists, search, recommendations, detail pages, or sitemap.
Current product boundary
Verified users can enable a single-account developer identity, upload games, and manage versions at /developer; super administrators govern users and games in the same console. Team collaboration, organization spaces, and settlement remain future capabilities. Platform code deployment and game-content publishing are separate flows.