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:
- ADR-0001 — Standalone Remote Gateway and Host
- ADR-0002 — Remote-Control Threat Model
- ADR-0003 — Gateway Trust & E2E-Encryption Model
- ADR-0004 — Cross-Platform Remote Host Scope
- ADR-0005 — MVP Release Artifact & Gates
- ADR-0006 — Control Room Placement
- ADR-0007 — QUIC/WebTransport Evaluation
Security, privacy & governance#
- Security Review
- Privacy & Legal Review
- Remote-Control Mode Allowance Matrix
- Security Regression Test Plan
Cloud & networking#
- Hetzner Reference Deployment (180.C.25.08)
- AWS Reference Deployment (180.C.25.09)
- Tailscale / WireGuard Private Network
- Deployment Smoke Test Plan
- Network Impairment Test Plan
- Performance Budget Test Plan
Per-tool adapters#
Blender
- Read-Only MVP on a Second MacBook
- Safe-Mutation MVP Closure
- Primitive Rollback & Undo
- Production-Command Hardware Verification
Unreal
Browser
- Profile Isolation
- Compensating Actions
- browser-use vs Direct CDP Evaluation
- Chrome Extension Value Evaluation
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
RemoteAdaptercontract, 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#
- Session Timeline & Audit Bundle
- Operator Workflow — Blender + Browser MVP
- MVP-Alpha Operations Runbooks
- MVP-Alpha SLOs & Error Budgets
- MVP-Alpha Soak Test Plan
- MVP-Alpha Architecture Stability
- MVP-Alpha Demo Scenarios
- MVP-Alpha Release Gate
- Operator Usability Study
- Release Gate Alignment
- Final GA Release Gate
Packaging, rollout & planning#
- macOS Packaging & Notarization Plan
- macOS Hardened Runtime, Entitlements & Notarization Recovery (180.C.26.11)
- MDM-Friendly & Offline / Private-Studio Install & Update (180.C.26.13)
- Remote-Host Update Channel & Rollback Plan
- Stage 26 — Two Logical Units (26.A / 26.B planning note) (180.C.26.17)
- Bridge Coexistence & Deprecation Plan
- Bridge Retirement Gate
- Compatibility Matrix
- Hardware Rig Inventory
- Local Cloud-Agent Simulation
- External Implementation Research (2026-04-21)
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).