Designing the Studio around playable artifacts

A game generator should not stop at a static demo card. The useful unit is a playable artifact that can be opened, inspected, refined, and published safely.

The Studio shape

The first V2 Studio slice uses four visible pieces:

• Composer — the user describes the game and submits a generation task.
• Stage timeline — queued, running, completed, failed, and recovery states are visible without a full-page spinner.
• Credit state — insufficient credits disables unsafe submission before the task starts.
• Artifact preview — generated HTML opens in a sandboxed preview route, not in the main app origin.

Why this matters

Better game quality comes from iterative control. A chat-style Studio lets the user refine mechanics, camera, difficulty, art direction, and publishing decisions instead of relying on one rigid prompt format.