Eve library

Bellona Remote Creative Control Plane — Documentation Index

Guide

Revision 1

On this page

The Remote Creative Control Plane (Phase 180.C) lets a trusted Oshun agent drive Blender, Unreal Engine, Chrome/Chromium, and selected desktop workflows on a second machine — over the LAN or a cloud tunnel — while an operator watches and approves through the Control Room. It is a standalone gateway (the authority) plus a host (on the controlled machine), both built on one authoritative wire protocol (@bellona/remote-protocol), with a hash-chained audit trail, per-command policy + approvals, and a cross-platform host runtime.

Start here#

If you want to… Read
Understand the system — topology, trust boundaries, protocol, gateway, host, Control Room, cloud Architecture (180.C.29.01)
Set it up / operate it — two-MacBook LAN, Hetzner/AWS, pairing, permissions, Blender/Unreal/browser, approvals, takeover, replay, uninstall User & Operator Guide (180.C.29.02)
Extend it — add a command, adapter, MCP tool, policy rule, approval gate, audit evidence, tests Developer Guide (180.C.29.03)
Write a third-party adapter — the RemoteAdapter contract, conformance, packaging, versioning/deprecation/migration Adapter SDK (180.C.32.08)
Sign & distribute an adapter — signed registry, ad-hoc trust model, publisher trust levels, org scope policy Adapter Distribution (180.C.32.09)
Run the whole spine locally in ~5 minutes (no Mac/Blender/cloud) Quickstart (180.C.29.13)
Port the host to a new OS — the platform-neutral permission/process/capture contract; Windows/Linux plug-in Host Permission Abstraction (180.C.29.16)

Architecture Decision Records#

The "why" behind the shapes the architecture doc describes:

Security, privacy & governance#

Cloud & networking#

Per-tool adapters#

Blender

Unreal

Browser

Desktop

Adapter SDK (third-party adapters)#

The published contract a third party implements to add a new tool, plus how such an adapter is verified, signed, and distributed.

  • Adapter SDK (180.C.32.08) — the RemoteAdapter contract, writing an adapter, the conformance suite, packaging/telemetry/policy-sandbox, and the versioning + deprecation policy.
  • Adapter SDK Migration Guide — a file-by-file walkthrough of migrating an adapter across a contract MAJOR bump.
  • Adapter Distribution (180.C.32.09) — signing, the signed registry, the ad-hoc trust model, publisher trust levels, and the org scope-policy controls.

Sessions, audit & operations#

Packaging, rollout & planning#

Code map (where the implementation lives)#

Component Package Path
Wire protocol (authoritative) @bellona/remote-protocol libs/bellona/remote-protocol/
Gateway (the authority) @bellona/remote-gateway apps/bellona/remote-gateway/
Host + adapters @bellona/remote-host apps/bellona/remote-host/
Adapter SDK (32.x) @bellona/remote-adapters libs/bellona/remote-adapters/
Cross-platform host runtime @bellona/host-runtime libs/bellona/host-runtime/
SDK client (29.04) @oshun/bellona-client libs/bellona/client/src/remote/
CLI (bellona remote …, 29.06) @bellona/cli apps/bellona/cli/src/commands/remote.ts
MCP gateway @bellona/mcp-gateway libs/bellona/mcp-gateway/
Control Room (operator UI) @bellona/control-room apps/bellona/control-room/
Browser extension @bellona/remote-extension apps/bellona/remote-extension/
Cloud IaC — deploy/bellona-remote/{hetzner,aws}/

The exhaustive per-task implementation tracker is implementation-tracker.md (very large — open with a pager).