Five ways in, one participant boundary

AI-driven sessions can arrive through different client protocols. DungeonQ’s self-hosted reference exposes the same bounded participant operations over HTTP, MCP, SSH, a PostgreSQL-profile interface, and a private Unix workload broker.

The transport and actor capability determine the context; the request payload cannot choose its own destination or authority. SSH provides no general shell, and the PostgreSQL profile is not a general SQL server.

These are real, bounded client paths into explicitly provisioned synthetic worlds. The reference does not automatically classify attacks or transparently intercept arbitrary host activity. The runtime guide documents the adapters and their limits: https://github.com/Ranopha/dungeonq-astra/blob/main/docs/RUNTIME.md