Documentation
MDL runs the engine; the game package shapes the experience
At runtime, MDL loads the selected game's prompt and configuration, reconstructs the current universe context, requests the next structured response, merges it into state, and renders the result for the player.
What the game package contributes
- The system prompt and opening files.
- The structured output contract and runtime UI metadata.
- Game-owned assets that define the world and presentation.
What MDL contributes
- The request lifecycle and prompt reconstruction.
- Save handling, state merging, and rendering.
- Account surfaces and the operational platform around the runtime itself.
Universe model
Player progress is stored as runtime universe state rather than as a single authored story path. This lets the platform continue a game session, revisit prior states, and reconstruct context for future requests.
Current reality
Today the runtime is still oriented around one selected package at a time. The long-term platform direction is request-scoped tenant resolution so different game hosts can load their own configuration through the same deployed engine.