Documentation
Shape a game package, then run it through MDL
MDL is meant to let a builder define a game once, then manage and publish it through a shared platform. The current workflow is already moving in that direction even though parts of the stack are still transitional.
1. Define the game package
Start by giving the game its own package with prompt files, openings, schemas, runtime UI metadata, and game-owned assets. This is where the game's identity should live.
2. Connect the package to MDL
MDL can run against the selected package and expose it through the shared engine. In development this may still use local package mode, while the longer-term platform model moves toward hosted package data.
3. Manage the game in the platform
Use the platform surfaces to review instructions, runtime presentation, assets, and other builder-facing controls. The goal is for game setup and publishing to happen from one platform home instead of from scattered ad hoc docs or one-off scripts.
4. Publish under the game's own identity
A hosted game should eventually present its own public domain and runtime while still benefiting from the shared MDL platform underneath.