design the game. we run the engine.

◉ the mechanism · what actually happens

One request, walked end to end — every step on your infrastructure, against your own models, with a human on the gate.

1. 01
   ChatMode

   You kick off a build, an asset pass, or a content drop in plain language — “cook the lighting bakes and stage the patch notes.” ChatMode plans the job and dispatches its built-in agents — planning, code, data-query, synthesis — to set the machinery in motion. No brittle batch script to babysit, no one watching a progress bar at midnight.

2. 02
   SmartModelRouter

   Each step routes to a model that fits it — a fast model to tag and sort assets, a long-context model to read a crash-report dump, a strong reasoner to triage a telemetry spike — across the providers you register. Bring your own models and run them on your own infrastructure; the unreleased build, the source, the design docs stay behind your walls.

3. 03
   CodeMode · Code Execution

   The glue work — the import scripts, the asset converters, the validators that catch a broken material before it ships — is written and run against your real codebase. CodeMode is an enterprise-platform capability that emits telemetry to your own monitoring inside your boundary — never your data, and nothing ever leaves your network; for one-shot transforms, Code Execution writes a throwaway tool, runs it sandboxed, and discards it. The pipeline code maintains itself.

4. 04
   AgenticWorkflows

   The build, the bakes, and the QA pass become a flow of named agents — repeatable, auditable, on rails. And there’s more behind sign-up: live-ops content flows that stage a drop, telemetry-triage flows that surface the patch that spiked crashes, QA agents that smoke-test a build, store-and-release prep that runs the submission checklist before you hit publish.

5. 05
   Credential isolation

   Agents reach your asset store, your build farm, and your storefront accounts as MCP tools, each call running under scoped, isolated credentials — never a shared studio token, never a secret in a prompt. Your source, your unreleased content, and your publisher keys stay yours.

6. 06
   Code Mode · build the studio tool, don’t wait for it

   The build tool, the asset pipeline, the editor extension you keep deferring — Code Mode drafts it on your stack and proves it with tests, gated by your review. You stay on the game itself; the agent clears the tooling backlog that would have eaten the milestone, so the studio you have ships more without anyone burning a sprint on plumbing.

7. 07
   HITL approval · Audit trail

   A step that ships a build or promotes an asset stops at the human gate — you approve the release before it goes, real architecture, not a checkbox. Every build and asset operation is written to an append-only audit log, so you have a clean, reproducible record of exactly how each artifact was made and who shipped it.

The pipeline runs itself, the build ships on your sign-off, and the record is already written — and that’s the build flow alone. The live-ops drops, the telemetry triage, and the QA agents are waiting behind sign-up.