# Bellona MVP Alpha and Final GA Release Gate Alignment

Status: `180.C.16.14` release-gate alignment contract.

Implementation date: 2026-04-23.

This note prevents the Stage 16 MVP alpha gate and the Stage `180.C.29.08`
through `.10` final GA gate from drifting into separate interpretations of what
"release ready" means. The source of truth is
`testing/bellona/remote-control/release-gate-alignment.ts`, with
`testing/bellona/remote-control/mvp-alpha-release-gate.ts` and
`testing/bellona/remote-control/final-ga-release-gate.ts` providing the
executable evidence gates for Stage 16 and Stage 29/30 respectively.

## Sources Reviewed

- `docs/domains/bellona/extras/remote-control/adr/ADR-0005-mvp-release-artifact-and-gates.md`
- `docs/domains/bellona/extras/remote-control/mvp-alpha-release-gate.md`
- `TODOS/phase-180.md`

## Required Stage Matrix

| Gate                        | Required stages                                                                            | Notes                                                                                                                                                                                                 |
| --------------------------- | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| MVP alpha artifact gate     | `180.C.01`-`.15`, then `180.C.16.01`-`.14`                                                 | The Stage 16 gate is the narrower macOS-first MVP artifact gate. It includes the deterministic hardening suites, SLO/error-budget policy, soak-plan definition, and this alignment contract.          |
| Final GA artifact gate      | Everything required by the MVP alpha gate, plus `180.C.17`-`.28`, then `180.C.29.01`-`.10` | The final GA gate is a strict superset. It adds production command breadth, SDK, CLI, packaging, governance, replay, final docs, final verification, release evidence, and final acceptance coverage. |
| Conditional GA scope stages | `180.C.36`, `180.C.37`                                                                     | Windows and Linux host stages are required unless release notes explicitly scope GA to macOS hosts and the waiver is accepted.                                                                        |

Two explicit non-rules matter just as much:

- `180.C.29.08`-`.10` cannot be checked off using only MVP alpha evidence.
- `180.C.29.11` and `.12` are completeness-audit and stage-closure work after
  the final GA gate, not prerequisites for the gate itself.

## Shared Release Criteria

The final GA gate inherits these MVP alpha requirements instead of replacing
them:

- protocol contracts and schema drift checks
- gateway, host, policy, approval, audit, and timeline verification
- Blender, browser, desktop fallback, Control Room, MCP or cloud-agent, and
  Unreal release surfaces
- deployment, security, performance, network, and operations evidence
- hardware or operator evidence whenever the rig inventory says CI is
  insufficient

## GA-Only Additions

The final GA gate adds work the MVP artifact intentionally postpones:

- Stage `180.C.17` through `180.C.28` production breadth
- Stage `180.C.29.08` final verification across format, lint, typecheck, unit,
  integration, contract, Playwright, security, performance, deployment smoke,
  and hardware-in-the-loop checks
- Stage `180.C.29.09` release evidence: logs, screenshots or stream captures
  where allowed, diagnostic bundles, security review, known risks, rollback
  plan, and compatibility matrix
- Stage `180.C.29.10` final product acceptance: same-LAN and cloud sessions,
  Blender, browser, desktop fallback, Unreal, artifact transfer, approvals,
  takeover, replay export, revocation, and uninstall

## Drift Prevention

The alignment and final-GA contracts now enforce these invariants in code:

1. The MVP alpha gate stage list is shared between `mvp-alpha-release-gate.ts`
   and `release-gate-alignment.ts`.
2. The final GA gate is recorded as a strict superset of the MVP alpha gate.
3. The conditional host-platform scope decisions stay explicit instead of
   getting lost in prose.
4. The final GA gate blocks unless `180.C.29.08`, `.09`, `.10`, `.12`, and
   `180.C.30.10` have attached verification, release evidence, acceptance, and
   fleet-closure evidence.

## Verification

```bash
pnpm exec vitest run --config vitest.config.ts tests/release-gate-alignment.test.ts tests/mvp-alpha-release-gate.test.ts --reporter=verbose
pnpm exec vitest run --config vitest.config.ts tests/final-ga-release-gate.test.ts --reporter=verbose
pnpm nx run-many -p @bellona/remote-control-testing -t lint,typecheck,test,build --skip-nx-cache --verbose
```
