Bindings

A binding is transport only. It maps the four primitives onto a wire and never invents state.

HTTP

route	method	maps to
`/observe`	GET	`observe()`
`/act`	POST `{id,verb?,value?}`	`act(...)`
`/wait_for`	POST `{predicate,timeoutMs}`	`waitFor(...)`
`/events?since=N`	GET	`events(N)`
`/health`	GET	liveness

import { bindings } from 'gamestruct'

const handle = bindings.http.createHandler(bridge, { token: process.env.DOOR_TOKEN })
// handle({ method, url, headers, body }) -> { status, headers, body }

The handler is runtime-agnostic: wire it to node:http, a Worker, or a test harness. When a token is set, every route except /health fails closed with 401 unless the request carries Authorization: Bearer <token>.

MCP (JSON-RPC 2.0)

initialize, tools/list, tools/call, plus observe and events as direct methods. Protocol version 2024-11-05.

const mcp = bindings.mcp.createHandler(bridge)
mcp({ id: 1, method: 'initialize' })
mcp({ id: 2, method: 'tools/list' })     // carries each tool's inputSchema
mcp({ id: 3, method: 'tools/call', params: { name: 'act__ui__start', arguments: { verb: 'activate' } } })

tools/list carries the full inputSchema so an MCP client auto-wires. An unknown method returns JSON-RPC error -32601.

Posture

identity — a seat is one authenticated actor; a door must not let one seat act as another. Local dev may run an open loopback posture; any non-loopback bind must require a token.
the gate — a door may mark verbs that need human sign-off (spend, trade, destroy). A gated verb parks, never silently executes.