# Bellona MVP Alpha Architecture Stability

Status: `180.C.16.10` stage-closure note.

Implementation date: 2026-04-23.

This note closes the Stage 16 MVP alpha hardening work. The goal is not to claim
GA or broad production readiness. The goal is to record that the Phase 180 MVP
architecture is now stable enough that deeper Blender, browser, Unreal,
deployment, security, and fleet stages can extend the same control plane without
replacing its core boundaries.

## Sources Reviewed

- `docs/domains/bellona/extras/remote-control/adr/ADR-0001-standalone-remote-gateway-and-host.md`
- `docs/domains/bellona/extras/remote-control/adr/ADR-0002-remote-control-threat-model.md`
- `docs/domains/bellona/extras/remote-control/adr/ADR-0003-gateway-trust-and-e2e-encryption-model.md`
- `docs/domains/bellona/extras/remote-control/adr/ADR-0005-mvp-release-artifact-and-gates.md`
- `docs/domains/bellona/extras/remote-control/implementation-tracker.md`
- `docs/domains/bellona/extras/remote-control/mvp-alpha-release-gate.md`
- `docs/domains/bellona/extras/remote-control/deployment-smoke-test-plan.md`
- `docs/domains/bellona/extras/remote-control/network-impairment-test-plan.md`
- `docs/domains/bellona/extras/remote-control/security-regression-test-plan.md`
- `docs/domains/bellona/extras/remote-control/performance-budget-test-plan.md`
- `docs/domains/bellona/extras/remote-control/mvp-alpha-operations-runbooks.md`

## Stable Architecture Invariants

The following surfaces are now treated as stable extension boundaries for later
Phase 180 work:

1. `libs/bellona/remote-protocol` remains the single source of truth for
   command, result, approval, audit, actor-chain, stream, and device schemas.
2. `apps/bellona/remote-gateway` remains the policy, approval, audit, session,
   device, and routing authority. Later stages may broaden capability coverage,
   but they should not move privileged decisions out of the gateway.
3. `apps/bellona/remote-host` remains outbound-only. Later stages may improve
   packaging, diagnostics, and adapters, but they should not require inbound
   MacBook control ports for the MVP path.
4. Adapter transports for Blender, browser, and Unreal remain localhost-only or
   in-process. Later stages may add richer capabilities, but they should not
   expose editor/browser ports directly to LAN or the internet.
5. Policy, approval, and audit remain in the command path for all privileged or
   mutating work. Later stages may add grants, planners, and safety logic, but
   they should not create hidden privileged bypasses.
6. The deterministic remote-control testing harness remains the reusable
   contract for regressions, with optional hardware and cloud evidence layered
   on top rather than replacing fixture coverage.
7. The MVP alpha release gate remains the release authority for Stage 16. Later
   stages may add evidence and stronger checks, but they should not redefine MVP
   alpha and GA as the same gate.

## What Future Stages Should Extend

The next Blender, browser, Unreal, deployment, security, and fleet stages should
build on the current architecture in these ways:

- add new protocol-owned commands instead of inventing new private envelopes
- plug new adapters and planners into the existing gateway-host dispatch path
- reuse policy preflight, approval metadata, actor chains, and audit emission
- add deterministic harness coverage first, then optional hardware or cloud
  evidence where CI cannot prove behavior
- attach new release evidence to the existing MVP alpha and final GA gates
- preserve the outbound-host, localhost-adapter, and no-hidden-privilege rules

## What Future Stages Should Not Replace

The current MVP architecture should not be replaced by:

- direct agent-to-adapter network control that bypasses the gateway
- LAN- or internet-exposed Blender, Chrome/CDP, or Unreal editor control ports
- arbitrary shell, arbitrary Blender Python, or real browser profile access as a
  default execution path
- a separate audit system that diverges from the protocol-owned command path
- a separate release gate that ignores the MVP alpha versus GA distinction

## Stability Statement

Stage 16 is stable enough to let later stages broaden capability and evidence
without re-architecting the core control plane because the following are now in
place and connected:

- protocol versioning, command metadata, actor chain, dry-run, and remediation
- gateway and host walking skeletons with policy, approval, and audit routing
- Blender, browser, desktop fallback, MCP, and Unreal MVP command paths
- deterministic network, security, performance, deployment, and release gates
- operator runbooks, deployment references, hardware inventory, and MVP docs

This is the threshold required by `180.C.16.10`. It does not imply that later
stages are optional; it means later stages now have a stable architecture to
extend.

## Verification

This is a documentation-only closure item. The committed verification is:

```bash
pnpm exec prettier --check TODOS/phase-180.md docs/domains/bellona/extras/remote-control/implementation-tracker.md docs/domains/bellona/extras/remote-control/mvp-alpha-architecture-stability.md
git diff --check
```
