query
Boundary state, schemas, the registry of what is saved and checksummed, every tool's manifest. A complete answer, or a loud refusal.
The AI surface
A running game answers four verbs: query, command, capture and control, with input injected through the same funnel a player uses. The engine exposes data and verbs; you bring the agent.
illustration · drawn in your browserAn illustration: the engine's four verbs played on the small browser simulation. The verbs are the engine's; the game is a sketch.
Four verbs
Boundary state, schemas, the registry of what is saved and checksummed, every tool's manifest. A complete answer, or a loud refusal.
The one write path. Commands are declared per tool; an undeclared command is refused, never quietly run. Each one is journaled and stamped with its tick.
{
"method": "pressstart.command.apply",
"params": {
"token": "<session token>",
"issuer": "agent:me",
"command": "spawn_prefab",
"payload": { "doc": "main.json", "prefab": "crate" }
}
}
Addressed pictures from a deterministic photo booth on one reference card. A turntable is a capture sequence: open the model and rotate it.
Pause, step any number of ticks, seed, checksum now, save, load, and input injected through the same funnel a player's input takes.
Ask it
Every tool lists its commands in a manifest. A command with no manifest entry fails the tool's build, and so does an entry with no command behind it. So "what can this engine do?" is a question with a complete answer, never a guess.
One door
The wire is a development tool. A shipped game never carries it, so the verbs your agent uses while you build are not a way into your players' machines.
On the road
The direction: an editor with your game beside it and one chat next to both, where every change, by a click or by an agent, is one undo away.