medialisted

# media Loki runs this. It carries the judgment, which backend, which model, the prompt, the read of the render, the lawful mark. Rendering itself is a backend call; the runnable client and the labeling pipeline are provisioned at first real use (see Provisioning). Until a backend is configured, the fallback is a design briefing the user renders elsewhere. ## Backends and routing Three standard backends, held in `registry.json`: - **Two connector backends** (host-configured MCP, interactive session), reached through the host's MCP tools. These are granted to Loki directly in its contract (`mcp__<server>__*`), so call them directly, **ToolSearch is main-loop-only and does not work inside a subagent**; never route a connector call through it. Async video polls for minutes. - **One key backend** (API key, runs unattended), driven by a generate script. The only path that survives a headless/scheduled run, because the connector sessions need an interactive login. **Availability first:** route only among the backends actually wired (read the connection records Wong writes), if just one is wired, use it; if the situationally-preferred class is not wired, fall back to whatever is. Among the wired ones, route by situation: **interactive design → a connector backend; unattended or scheduled runs → the key backend.** Wong configures a backend once (the connection and, only for the key backend, the secret); you then use it directly and never wire or hold a secret yourself. No backen