Eve library

Bellona MVP Alpha Release Gate

Guide

Revision 1

On this page

Status: 180.C.16.09 deterministic gate plan and evaluator.

Implementation date: 2026-04-23.

This gate translates ADR-0005 into a concrete, reusable release checklist for the MVP alpha artifact. It does not certify the release by itself. Instead, it blocks release until the required completed stages, documentation bundle, demo scenarios, deterministic hardening suites, package verification results, and hardware or cloud evidence are all attached.

Sources Reviewed#

Normative release criteria:

  • docs/domains/bellona/extras/remote-control/adr/ADR-0005-mvp-release-artifact-and-gates.md

Implementation and verification references:

  • docs/domains/bellona/extras/remote-control/implementation-tracker.md
  • docs/domains/bellona/extras/remote-control/mvp-alpha-operations-runbooks.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-slos-and-error-budgets.md
  • docs/domains/bellona/extras/remote-control/mvp-alpha-soak-test-plan.md
  • docs/domains/bellona/extras/remote-control/release-gate-alignment.md
  • docs/domains/bellona/extras/remote-control/blender-read-only-mvp-second-macbook.md
  • docs/domains/bellona/extras/remote-control/blender-safe-mutation-mvp-closure.md
  • docs/domains/bellona/extras/remote-control/operator-workflow-blender-browser-mvp.md
  • docs/domains/bellona/extras/remote-control/unreal-readonly-safe-mutation-mvp-closure.md
  • docs/domains/bellona/extras/remote-control/session-timeline-and-audit-bundle.md
  • docs/domains/bellona/extras/remote-control/hardware-rig-inventory.md

Gate Structure#

testing/bellona/remote-control/mvp-alpha-release-gate.ts exposes:

  • createRemoteControlMvpAlphaReleaseGatePlan()
  • createPassingRemoteControlMvpAlphaEvidenceSnapshot()
  • evaluateRemoteControlMvpAlphaReleaseGate()

The plan requires:

  • completed stages 180.C.01 through 180.C.15
  • completed hardening items 180.C.16.01 through 180.C.16.08
  • completed gate-hardening items 180.C.16.09 through 180.C.16.14
  • the MVP docs bundle called out by ADR-0005
  • demo scenarios MVP-01 through MVP-10
  • release-gate checks covering:
    • protocol
    • gateway
    • host
    • policy and audit
    • Blender
    • browser
    • desktop fallback
    • Control Room
    • MCP and cloud-agent
    • Unreal
    • deployment smoke
    • security regression
    • performance budgets
    • network impairment
    • SLO error-budget policy

Evaluation Rules#

The evaluator runs the deterministic Stage 16 suites directly:

  • deployment smoke
  • security regression
  • performance budgets
  • network impairment
  • MVP alpha SLO policy

It then merges those suite results with an explicit evidence snapshot for:

  • package/build/test/e2e verification that lives outside this package
  • documentation bundle publication
  • demo-scenario evidence
  • hardware and cloud evidence that CI cannot infer

Gate-check and demo-scenario evidence must be attached as structured records, not only as bare checklist IDs. A valid record names the requirement ID, record kind, pass status, canonical UTC millisecond timestamp, unique artifact IDs, evidence kinds, and the planned command, full 40-character commit SHA, CI environment, operator ID, and concrete rig IDs wherever that evidence type requires them. Placeholder suffixes, rollover timestamps, duplicate records, case-variant duplicate artifact IDs, reused artifact IDs across evidence groups, generic rig IDs, and artifacts that do not name the required evidence slot keep the gate blocked.

The evaluator returns:

  • blocked when any required stage, doc item, demo scenario, or gate check is missing or when any structured evidence record is invalid
  • warning when deterministic suites surface non-blocking risk, such as the fixture-only LAN, Hetzner, or AWS deployment smoke results without attached live cloud deployment evidence, the TURN placeholder without attached live evidence, or a low-but-still-positive SLO budget
  • passed only when the full MVP alpha evidence snapshot is attached

Required Verification Inputs#

The gate plan records the exact commands that must be attached for the major surfaces:

  • protocol: pnpm nx contracts:check @bellona/remote-protocol --skip-nx-cache --verbose
  • gateway: pnpm nx run-many -p @bellona/remote-gateway -t lint,typecheck,test,build --skip-nx-cache --verbose
  • host: pnpm nx run-many -p @bellona/remote-host -t lint,typecheck,test,build --skip-nx-cache --verbose
  • Control Room: pnpm nx run-many -p @bellona/control-room -t lint,typecheck,test,build --skip-nx-cache --verbose and pnpm nx e2e @bellona/control-room --skip-nx-cache --verbose
  • MCP/cloud-agent: pnpm nx run-many -p @bellona/mcp-gateway -t lint,typecheck,test,build,cloud-agent:mvp-smoke,remote-mac:no-inbound-smoke --skip-nx-cache --verbose
  • Blender/browser/desktop/Unreal: the committed remote smoke commands under apps/bellona/remote-host/project.json
  • Stage 16 deterministic suites: the focused tests/*.test.ts commands in testing/bellona/remote-control

Release Semantics#

This gate is intentionally narrower than the final GA gate in 180.C.29.08 through .10.

  • Stage 16 can pass with documented TURN placeholder limits and without GA-only production breadth.
  • Stage 16 cannot pass without the MVP docs bundle, demo evidence, package verification, and the required two-MacBook or cloud evidence.
  • Stage 29 still owns final GA verification, broader production command coverage, release docs, SDK parity, and final acceptance.
  • docs/domains/bellona/extras/remote-control/release-gate-alignment.md is the explicit stage-matrix contract tying the two gates together.

Verification#

The committed automated gate is:

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

The first command proves the gate structure, default blocking behavior, full pass path with attached structured evidence, and regressions on omitted, malformed, duplicate, placeholder, stale, and reused evidence records. The second command keeps the reusable gate buildable alongside the rest of the remote-control testing package.