- Status: Accepted
- Date: 2026-04-22
- Authors: Bellona Remote Control Working Group, Codex
- Reviewers: Bellona, Psyche, Yemaya, Oshun Platform, Oshun Security
Context and Problem Statement#
Phase 180 uses several gate names: MVP, Alpha Hardening, stable release, final
verification, and GA-style final release. The checklist now labels 180.C.16 as
Alpha Hardening and MVP Release Gate, while 180.C.29 is
Final Verification, Documentation, SDKs, and Release. Some older wording still
says that 180.C.16.09 gates a "stable release", which conflicts with the later
final verification and acceptance tasks in 180.C.29.08-.10.
Without a single release-artifact definition, future agents can accidentally ship too little at MVP, overblock MVP on production-stage work, or treat the final release gate as redundant. This ADR defines what the Phase 180 MVP artifact is, which stages must be complete for it, which demo scenarios must pass, which documentation ships, and how the Stage 16 and Stage 29 gates relate.
Decision Drivers#
- Keep the first usable release focused on the macOS-first remote creative control path chosen in ADR-0004.
- Require enough policy, approval, audit, timeline, and hardware evidence before mutating remote creative tools are considered MVP-ready.
- Avoid blocking MVP on production coverage stages that intentionally come after the MVP, such as Blender production commands, browser production automation, Control Room production experience, Unreal production coverage, fleet expansion, and Windows/Linux host parity.
- Preserve a stronger final gate for GA/releasable production use.
- Make demo scenarios concrete enough that release evidence cannot be hand-waved.
Considered Options#
Option 1: Treat 180.C.16 as the Final Stable Release Gate#
The first hardening gate would ship the stable product and make later production coverage stages optional enhancements.
This option is rejected. It contradicts the ordering of production Blender,
browser, Control Room, Unreal, networking, packaging, security, operations, SDK,
and final acceptance stages that follow 180.C.16.
Option 2: Treat 180.C.29 as the Only Release Gate#
MVP language before Stage 29 would be treated as development scaffolding, and no MVP artifact would ship until final verification.
This option is rejected. It would remove the product value of the Phase 180 MVP stages and delay feedback on the control plane until after broad production coverage work.
Option 3: Two Explicit Gates: MVP Alpha at 180.C.16, Final GA at 180.C.29#
Stage 16 ships a controlled, macOS-first MVP alpha artifact. Stage 29 ships the final GA/releasable artifact after production coverage, documentation, SDKs, hardware evidence, security, operations, and acceptance scenarios are complete.
This option is chosen.
Decision Outcome#
Bellona adopts a two-gate release model:
- MVP Alpha Artifact Gate (
180.C.16): a macOS-first, operator-supervised, policy-gated release artifact suitable for internal dogfooding and tightly controlled pilot use. It proves the architecture end to end on the MVP path. - Final GA Artifact Gate (
180.C.29): a documented, SDK-accessible, operator-usable, production-release candidate after production command coverage, hardening, evidence, deployment, security, and acceptance work.
180.C.16.09 is interpreted as the MVP alpha release gate, not the final
stable/GA gate. 180.C.29.08-.10 remain the final verification, release
evidence, and product acceptance gate.
MVP Alpha Artifact#
The MVP alpha artifact ships as a versioned source commit plus reproducible local builds and deployment instructions for:
libs/bellona/remote-protocolgenerated contracts and schema ownership docs.apps/bellona/remote-gatewaywith durable-enough MVP storage, device/session lifecycle, command routing, policy, approval, audit, timeline, and local/cloud deployment smoke paths.apps/bellona/remote-hostfor macOS-first controlled-host operation with development-to-production credential migration path and host outbound connection.- Bellona Control Room MVP for device list, session timeline, approvals, screenshot/stream placeholder, pause/stop, and operator workflow.
- MCP/cloud-agent MVP tools that cannot bypass gateway policy, approvals, revocation, command schemas, or audit.
- Blender read-only scene info and safe primitive creation through the remote path with audit, approval where required, rollback/undo notes, and evidence.
- Browser managed-profile launch, navigation, snapshot, screenshot, and cleanup through localhost-only host automation.
- Desktop fallback MVP for explicitly allowlisted macOS screenshot/window/focus and click behavior with permission diagnostics and visual verification.
- Unreal MVP for project/world read-only query and first safe actor spawn using the same policy, audit, evidence, and approval path.
- Audit/timeline export sufficient for the MVP scenarios.
- Release evidence bundle linked from the implementation tracker.
The MVP alpha artifact is not a broad production automation release. It does not require Windows or Linux hosts, Tier-2 DCC adapters, production Blender command coverage, production browser automation, full Control Room production experience, fleet scheduling, GA SDK parity, or old-bridge removal.
Stages Required for MVP Alpha#
The MVP alpha gate requires these stages complete:
180.C.01Phase control and ground rules.180.C.02audit notes, ADRs, compatibility, trust, hardware, and MVP artifact decisions.180.C.03protocol package and contract drift checks, including added pre-MVP protocol refinements if they are needed by security gates.180.C.04mock harness and contract tests.180.C.05remote gateway walking skeleton and command routing.180.C.06remote host walking skeleton.180.C.07pairing, auth, policy, approvals, and audit coverage.180.C.08audit, observability, timeline, artifact metadata, redaction, logging, metrics, and audit-failure behavior.180.C.09Blender read-only adapter MVP.180.C.10Blender safe mutation MVP.180.C.11browser CDP MVP.180.C.12live stream and minimal Control Room MVP, with screenshot-only mode accepted before full WebRTC if documented.180.C.13desktop fallback MVP.180.C.14MCP and cloud-agent MVP.180.C.15Unreal read-only and safe mutation MVP.180.C.16alpha hardening and MVP release gate.
Items added after Stage 16 may be started later but are not MVP alpha blockers unless a later ADR explicitly promotes them.
MVP Alpha Demo Scenarios#
All MVP alpha demo scenarios must pass and produce release evidence:
| Scenario ID | Scenario | Required Rigs / Modes | Evidence |
|---|---|---|---|
MVP-01 |
Pair two Macs on same LAN, start a session, list device capabilities. | MAC-OP-01, MAC-HOST-01, same-LAN gateway |
Pairing audit entry, device registry state, session timeline, capability report. |
MVP-02 |
Query Blender scene info through gateway -> host -> adapter. | MAC-HOST-01, Blender baseline |
Scene-info result, adapter health, audit/timeline entries, fixture scene version. |
MVP-03 |
Create one Blender primitive with policy, approval if required, and undo. | MAC-HOST-01, Blender baseline |
Approval decision, before/after scene info, undo checkpoint, audit entries, rollback note. |
MVP-04 |
Launch isolated browser, navigate, snapshot, screenshot, and close. | MAC-HOST-01, Chrome for Testing or Playwright Chromium |
Browser profile path, CDP localhost proof, screenshot artifact, audit/timeline entries. |
MVP-05 |
Use desktop fallback against an allowlisted macOS window. | MAC-HOST-01, Screen Recording and Accessibility granted |
Permission report, window list/focus, screenshot, visual click verification, audit/timeline entries. |
MVP-06 |
Operator approves, denies, pauses/stops, and replays a session. | MAC-OP-01, Control Room MVP |
Control Room test output, approval records, pause/stop events, replay/export artifact. |
MVP-07 |
Cloud-agent smoke flow through one reference cloud gateway. | MAC-HOST-01, one cloud rig, optional TURN placeholder |
Device list, session start, Blender query, browser screenshot, session stop, gateway logs, audit export. |
MVP-08 |
Unreal MVP read-only query and first safe actor spawn. | MAC-HOST-01, Unreal baseline |
Project/world query, spawn result, policy/audit/evidence, timeout/cancel behavior where applicable. |
MVP-09 |
Revoked host and denied policy cannot execute commands. | MAC-HOST-01, gateway tests and local smoke |
Revocation result, denied command result, no host dispatch, audit entries. |
MVP-10 |
Network impairment smoke for reconnect and degraded mode. | NET-IMPAIR-01, same-LAN or cloud gateway |
Packet-loss/high-latency run, host reconnect, command timeout/degraded state, audit continuity. |
Documentation Shipped at MVP Alpha#
The MVP alpha docs bundle must include:
- Architecture overview for topology, trust boundaries, gateway authority, host enforcement, protocol ownership, adapter boundaries, and MCP/Control Room client roles.
- Operator runbook for two-MacBook LAN setup, cloud gateway setup, pairing, permissions, approvals, pause/stop/takeover, replay/export, revocation, and uninstall.
- Developer guide for adding commands, adapters, policy rules, approval gates, audit evidence, and tests.
- Hardware rig inventory and compatibility matrix.
- Security/trust docs covering prompt injection, browser profile isolation, desktop fallback limits, path grants, revocation, redaction, and audit retention.
- Troubleshooting runbooks for permissions, plugin repair, stream failure, gateway restart, host reconnect, audit export, update rollback, and diagnostic bundles.
- Known limitations and explicit non-MVP surfaces: Windows/Linux hosts, real browser profiles, arbitrary shell, arbitrary Blender Python, Unreal console, production browser automation, full fleet scheduling, Tier-2 DCC adapters, and old bridge removal.
Final GA Gate#
The final GA artifact remains governed by 180.C.29.08-.10 and requires the
broader checklist to be complete or explicitly blocked with an accepted waiver.
It includes:
- Production Blender command coverage (
180.C.17,180.C.18). - Browser production automation and optional external browser-agent decisions
(
180.C.19,180.C.20). - Control Room production experience (
180.C.21). - File/artifact/cross-app workflow coverage (
180.C.22). - Unreal production command, Sequencer, render, build, and diagnostics coverage
(
180.C.23,180.C.24). - Networking, cloud deployment, transport, and streaming hardening (
180.C.25). - macOS packaging, permissions, signing, updates, diagnostics, SBOM, and
cross-platform abstraction docs (
180.C.26). - Security, privacy, governance, observability, replay, SDK, CLI, final docs,
release evidence, and acceptance (
180.C.27-180.C.29).
Windows and Linux host stages (180.C.36, 180.C.37) are Phase 180 expansion
work per ADR-0004. They are not MVP alpha blockers. A final GA release may ship
without Windows/Linux only if the release notes explicitly scope GA to macOS
hosts and 180.C.36/180.C.37 remain unchecked or blocked with an accepted
scope waiver.
Normative Rules#
- Do not call the Stage 16 artifact stable or GA.
- Do not check
180.C.16.09unless all MVP alpha required stages, demo scenarios, docs, verification, and evidence are complete. - Do not check
180.C.29.08-.10based only on MVP alpha evidence. - Every MVP demo scenario must include automated test output where possible and hardware/manual evidence where the hardware inventory says CI is insufficient.
- Any missing MVP demo scenario must block MVP alpha unless an accepted ADR changes the MVP scope.
- Future final release notes must clearly state whether the release is MVP alpha, macOS GA, or cross-platform GA.
Acceptance Criteria#
- This ADR exists under
docs/domains/bellona/extras/remote-control/adr/. - The decision defines the MVP alpha artifact and final GA artifact separately.
- The ADR lists stages required for MVP alpha.
- The ADR lists MVP demo scenarios and documentation shipped at MVP alpha.
- The ADR resolves the
180.C.16.09versus180.C.29.08-.10ambiguity. - The tracker row and Phase 180 checklist item for
180.C.02.16are updated. - Markdown formatting verification passes for this ADR, the tracker, and the phase checklist.
Consequences#
Positive consequences:
- Future agents have one source of truth for what MVP alpha means.
- Stage 16 can produce real feedback without pretending production coverage is done.
- Stage 29 retains its stronger final verification role.
- Demo scenarios give release evidence concrete shape.
Negative consequences:
- Some checklist text and future rows must honor the new alpha/GA distinction.
- The MVP remains a controlled pilot artifact, not a broad customer release.
- Final GA may still require scope decisions if Windows/Linux remain incomplete.
Related Decisions#
docs/domains/bellona/extras/remote-control/adr/ADR-0001-standalone-remote-gateway-and-host.mddocs/domains/bellona/extras/remote-control/adr/ADR-0002-remote-control-threat-model.mddocs/domains/bellona/extras/remote-control/adr/ADR-0003-gateway-trust-and-e2e-encryption-model.mddocs/domains/bellona/extras/remote-control/adr/ADR-0004-cross-platform-remote-host-scope.mddocs/domains/bellona/extras/remote-control/compatibility-matrix.mddocs/domains/bellona/extras/remote-control/hardware-rig-inventory.md- Future
180.C.16.09and180.C.16.11release-gate implementation. - Future
180.C.29.08-.10final verification and acceptance.
References#
TODOS/phase-180.mdTODOS/phase-180-gaps.mddocs/domains/bellona/extras/remote-control/implementation-tracker.md