Glossary and limits

Use these terms consistently when designing missions or discussing an MCP changeset.

Core terms

• Workspace: the author access boundary containing campaigns and AI connections.
• Campaign: a collection of missions, endings, resources, and a top-level route.
• Draft: the mutable authoring version. It carries an editVersion for concurrent writes.
• Revision: an immutable published snapshot of a validated campaign.
• Mission: one playable workflow with its own graph of typed nodes.
• Node: a story, interaction, or flow-control step in a mission.
• Edge: a directed connection between mission nodes.
• Port: a named output or input used to connect an edge. Choices and exits may have several named outputs.
• Transition: a campaign-level route from a named mission exit to another mission or an ending.
• Resource: a reusable location, content record, ending, or media reference.
• Playtest: an author-only run built from one frozen draft version.
• Production link: an invitation to a published player run, managed in Studio.
• Grant: a connection's permissions and allowed campaigns.
• Request ID: a UUID identifying one logical MCP write for safe retries.
• Alias: a name for an entity created earlier in one MCP changeset.

Product boundaries

Campaign Studio is the author interface; the Player Terminal is the player's interface. The editor can author puzzles, choices, uploads, endings, and manual rewards. The platform stores screenshot evidence but does not automatically recognize its contents. It does not conduct open-ended real-time AI dialogue or deliver an in-game item automatically.

The MCP tools cover draft authoring and playtests. Publishing, production links, and player-run operations are handled in Studio. Remote MCP currently uses a bearer token; OAuth client login is a future capability.

The example campaign Before Dawn is an acceptance example for reusable mechanics. Its story, codes, and mission names are not hard-wired into the editor.