Inventory date: 2026-04-22
Scope: 180.C.02.15
This matrix defines the physical and virtual rigs required to sign off Phase 180 items that cannot be fully proven in CI. It complements the compatibility matrix and ADR-0004. It does not mark any downstream item complete; it defines the evidence floor future tasks must meet before checking hardware-gated work.
Evidence Rules#
- Hardware-gated items must name the rig ID, OS version, app version, browser channel, network mode, evidence artifact, date, and operator in the implementation tracker.
- Virtual machines are acceptable for packaging, service lifecycle, protocol, update, and non-capture smoke tests. They are not acceptable as sole evidence for screen capture, desktop input, WebRTC media, GPU render behavior, Blender UI behavior, Unreal Editor behavior, or macOS TCC permission flows.
- Browser evidence must distinguish Playwright-managed Chromium, Chrome for Testing, branded Chrome Stable/Beta, and Microsoft Edge where applicable.
- DCC evidence must include the app version, plugin/addon version or commit, fixture project/scene, command path, and rollback/evidence artifacts.
- Network evidence must record whether the gateway is local LAN, cloud, TURN relay, direct ICE, VPN/tunnel, or degraded/offline.
- If a rig is unavailable, the tracker row must stay blocked or record a narrower claim. Do not substitute local mock tests for hardware evidence.
Required Rig IDs#
| Rig ID | Kind | Required OS / Runtime Baseline | Required Apps / Channels | Primary Purpose | Virtualization Policy |
|---|---|---|---|---|---|
MAC-OP-01 |
Physical | macOS 14 Sonoma or macOS 15 on Apple Silicon | Chrome Stable, Chrome Beta or Chrome for Testing, Playwright browsers, pnpm 10.25.0, Node 20/22 | Operator laptop, local gateway, Control Room, MCP/client smoke, same-LAN source network | Physical required for multi-display, notifications, local-network, and operator workflow evidence. |
MAC-HOST-01 |
Physical | macOS 14 Sonoma on Apple Silicon | Blender 4.0.x baseline, Blender 4.2 LTS or 4.5 LTS candidate, Unreal 5.3 baseline, Chrome Stable, Chrome for Testing, Playwright browsers | MVP controlled MacBook Remote Host: TCC, Keychain, LaunchAgent, ScreenCaptureKit, Accessibility | Physical required. VM evidence cannot replace TCC, screen capture, input, sleep/wake, or DCC UI signoff. |
MAC-HOST-02 |
Physical | macOS 15 on Apple Silicon | Blender 4.5 LTS, Unreal 5.6 candidate, Chrome Stable/Beta, Chrome for Testing, Playwright browsers | Candidate advanced capture, HDR/wide-gamut, newer Unreal, codec, and update compatibility | Physical required for media, codec, capture, and update evidence; optional until candidate support is claimed. |
MAC-HOST-03 |
Physical | macOS 26.5.x on Apple Silicon (MacBook Air, 16 GB) | Xcode 26.5 / Swift 6.3.x toolchain, Node 24, pnpm 10.25.0, Blender 4.5.x, Chrome Stable | Current-macOS Remote Host evidence rig: native menu-bar shell, launchd LaunchAgent lifecycle, Keychain identity paths (180.C.26.01/180.C.26.02 closure runs, 2026-07-07) |
Physical required. Registered 2026-07-07 because MAC-HOST-01/-02 baselines (macOS 14/15) no longer match current physical hardware; TCC, launchd, and Keychain evidence must come from a real login session. |
LAN-GW-01 |
Physical | macOS 14/15 or Linux LTS host on the same LAN | Node 20/22, pnpm 10.25.0, Bellona Remote Gateway, optional local TURN | Same-LAN gateway, pairing, reconnect, command round trip, audit replay, emergency stop | VM allowed only if network behavior is not the signoff target. |
CLOUD-HETZNER-01 |
Virtual | Ubuntu 24.04 LTS or supported provider Linux image | Node 20/22, gateway runtime, Postgres/Redis or selected stores, TURN, object storage or compatible fixture, TLS certificates | Hetzner cloud gateway smoke, host outbound WSS, TURN relay, deployment runbooks | VM is expected; must be provider-hosted for deployment evidence. |
CLOUD-AWS-01 |
Virtual | Amazon Linux 2023 or Ubuntu 24.04 LTS on AWS | Node 20/22, gateway runtime, managed or self-hosted data stores, TURN, object storage, TLS/load balancer | AWS reference deployment, cross-network smoke, backups, observability, gateway restart evidence | VM/cloud instance is expected; local emulation is not enough for AWS deployment signoff. |
WIN-HOST-01 |
Physical | Windows 11 Pro or Enterprise 24H2 on a GPU workstation | Blender 4.5 LTS, Unreal 5.6 candidate, Chrome Stable/Beta, Chrome for Testing, Microsoft Edge Stable, Windows Service runtime, signed MSI fixture | Windows Remote Host, DCC workstation, DXGI capture, Defender/UAC, Edge/Chrome CDP, update rollback | Physical required for DXGI, Defender, UAC, GPU, desktop input, DCC UI, and installer evidence. |
WIN-VM-01 |
Virtual | Windows 11 Pro/Enterprise 24H2 VM | Signed MSI fixture, Windows Service runtime, Chrome/Edge Stable, test certificates | Packaging, service lifecycle, diagnostic bundle, update manifest, non-GPU protocol smoke | VM allowed only for non-capture/non-GPU/non-input evidence. |
LINUX-RENDER-01 |
Physical | Ubuntu 24.04 LTS or studio-selected Linux LTS with GPU | Blender 4.5 LTS, Unreal commandlet/editor candidate, Chrome/Chromium Stable if browser support is claimed, systemd user services, PipeWire, VA-API/NVIDIA stack | Linux render-node/headless host, Blender/Unreal commandlet, PipeWire/audio, codec, diagnostics | Physical required for GPU render, codec, PipeWire, and desktop capture claims. |
LINUX-VM-01 |
Virtual | Ubuntu 24.04 LTS VM | deb/rpm/AppImage fixtures, systemd user services, Chrome/Chromium Stable, headless Blender where supported | Linux package install, service lifecycle, protocol smoke, non-GPU headless adapter tests | VM allowed for packaging and headless smoke only. |
MOBILE-IOS-01 |
Physical | Current supported iOS/iPadOS Safari | Safari, installed PWA where applicable, APNs-capable device | Approval-only mobile PWA, push notification, responsive Control Room approval flow | Physical required for push, PWA install, and mobile viewport signoff. |
MOBILE-ANDROID-01 |
Physical | Current supported Android with Chrome | Chrome Stable, installed PWA where applicable, FCM-capable device | Approval-only mobile PWA, push notification, responsive approval flow | Physical required for push, PWA install, and mobile viewport signoff. |
NET-IMPAIR-01 |
Either | Linux/macOS network test host with controllable impairment | Network impairment tooling, packet loss/latency controls, local DNS/TURN fixtures | High-latency, packet-loss, reconnect, TURN fallback, gateway restart, backpressure, degraded mode QA | VM allowed for command-path tests; physical networks required for final same-LAN/cross-network evidence. |
Version Baselines#
| Surface | MVP Baseline | Candidate / Expansion Range | Notes |
|---|---|---|---|
| macOS host OS | macOS 14 Sonoma on Apple Silicon | macOS 15 for advanced capture, HDR, and newer Unreal validation | Intel Macs are not MVP hosts unless a later task explicitly adds them. |
| Windows host OS | Not an MVP blocker | Windows 11 Pro/Enterprise 24H2 physical GPU workstation and VM | Required when 180.C.36 begins. |
| Linux host OS | Not an MVP blocker | Ubuntu 24.04 LTS physical render node and VM | Required when 180.C.37 begins; studio-selected distro may be added with evidence. |
| Blender | Blender 4.0.x on MAC-HOST-01 |
Blender 4.2 LTS and 4.5 LTS on macOS, Windows, and Linux | Hardware smoke notes must include addon version/commit and fixture scene. |
| Unreal | Unreal 5.3 on MAC-HOST-01 |
Unreal 5.4, 5.5, and 5.6 on macOS/Windows; commandlet/render on Linux | Hardware evidence must identify fixture project, plugin version/commit, and GPU mode. |
| Browser automation | Playwright Chromium and Chrome for Testing | Branded Chrome Stable/Beta; Edge Stable on Windows | Real personal profiles remain blocked until future policy/approval tasks allow them. |
| WebRTC / streaming | Gateway-signaled screenshot placeholder, then LAN | TURN relay, direct ICE, cloud gateway, HDR, codec selection | Command control must remain independent of media success. |
| Mobile approval | Not needed for first Control Room MVP | iOS Safari PWA and Android Chrome PWA | Required before mobile approval/push tasks are checked. |
| Cloud gateway | Local fake and same-LAN gateway first | Hetzner and AWS reference deployments | Cloud evidence requires real provider deployment, not only Docker/local emulation. |
Hardware-Gated Checklist Mapping#
| Item / Stage Range | Required Rigs | Required Evidence Before Checkoff |
|---|---|---|
180.C.09.07, 180.C.09.10 |
MAC-HOST-01; optional LINUX-VM-01 for headless smoke |
Blender opens fixture scene, addon/adapter reports version, blender.scene.info returns scene data through the remote path. |
180.C.10.07, 180.C.10.10 |
MAC-HOST-01 |
Blender primitive creation in fixture scene with undo checkpoint, before/after scene-info evidence, audit entries, and rollback notes. |
180.C.11.04-180.C.11.10 |
MAC-HOST-01, MAC-OP-01; later WIN-HOST-01 for Edge/Windows parity |
Isolated profile launch, localhost-only CDP, navigate, snapshot, screenshot, close, blocked profile/default profile behavior. |
180.C.12.06-180.C.12.10 |
MAC-OP-01, MAC-HOST-01, LAN-GW-01, NET-IMPAIR-01; later CLOUD-HETZNER-01 or CLOUD-AWS-01 |
Control Room device/session/timeline/approval flow, screenshot placeholder or WebRTC stream, pause/stop, reconnect, TURN/direct status. |
180.C.12.13, 180.C.12.14 |
MAC-OP-01, MOBILE-IOS-01, MOBILE-ANDROID-01 |
Desktop notification and mobile approval PWA evidence, push/permission behavior, approve/deny latency, responsive layout screenshots. |
180.C.13.01-180.C.13.10 |
MAC-HOST-01, MAC-OP-01 |
Screen Recording and Accessibility permission detection, window list/focus, screenshot artifact, coordinate mapping, allowlisted click verify. |
180.C.13.12-180.C.13.14 |
MAC-HOST-01; later WIN-HOST-01, LINUX-RENDER-01 where claimed |
Keyboard layout detection, multi-display stable identity, clipboard capture redaction, before/after evidence. |
180.C.14.06-180.C.14.09 |
MAC-HOST-01, MAC-OP-01, LAN-GW-01, CLOUD-HETZNER-01 or CLOUD-AWS-01 |
Cloud-agent smoke: list device, start session, query Blender, navigate browser, screenshot, stop session, audit replay. |
180.C.15.05-180.C.15.10 |
MAC-HOST-01; optional WIN-HOST-01 when Windows Unreal support is claimed |
Unreal plugin connection, project info/world query, safe actor spawn, screenshot/evidence placeholder, timeout/cancel/restart notes. |
180.C.16.02, 180.C.16.07, 180.C.16.08 |
MAC-HOST-01, MAC-OP-01, LAN-GW-01, CLOUD-HETZNER-01, CLOUD-AWS-01, NET-IMPAIR-01 |
Signed/notarized packaging evidence or plan, two-Mac LAN runbook, local/LAN/cloud deployment smoke, gateway restart, host reconnect. |
180.C.17.09, 180.C.17.10 |
MAC-HOST-01; optional WIN-HOST-01, LINUX-RENDER-01 for expansion claims |
Hardware/headless notes for each Blender production command, fixture scene, evidence artifacts, rollback/undo behavior. |
180.C.18.05-180.C.18.10 |
MAC-HOST-01, MAC-HOST-02; optional LINUX-RENDER-01 for render-node claims |
Advanced Blender render/viewport/render artifact evidence, privileged Python approval path, simulation/render timing and rollback notes. |
180.C.19.01-180.C.20.10 |
MAC-HOST-01, MAC-OP-01; later WIN-HOST-01; browser channels from the version matrix |
Browser production automation, prompt-injection fixtures, downloads/uploads, traces, extension/browser-agent comparison, profile isolation. |
180.C.21.03-180.C.21.20 |
MAC-OP-01, MAC-HOST-01, MOBILE-IOS-01, MOBILE-ANDROID-01, NET-IMPAIR-01 |
Stream switching, overlays, replay view, accessibility tests, mobile/responsive evidence, usability test artifacts. |
180.C.22.06-180.C.22.14 |
MAC-HOST-01, MAC-OP-01; optional WIN-HOST-01, LINUX-RENDER-01 for cross-app claims |
Cross-app asset transfer, Blender-to-Unreal flow, render-to-Yemaya flow, browser-to-asset action, project-root grants, artifact hashes. |
180.C.23.08-180.C.24.10 |
MAC-HOST-01; WIN-HOST-01 when Windows Unreal parity is claimed |
Unreal map/actor/material/asset/console allowlist, viewport/camera, render queue, diagnostics, build/cook/package evidence. |
180.C.25.01-180.C.25.17 |
MAC-OP-01, MAC-HOST-01, LAN-GW-01, CLOUD-HETZNER-01, CLOUD-AWS-01, NET-IMPAIR-01, MAC-HOST-02 |
mDNS/LAN, outbound tunnel, TURN relay, channel separation, impairment tests, cloud deployments, codec/bitrate/HDR/multi-track evidence. |
180.C.26.01-180.C.26.16 |
MAC-HOST-01, MAC-HOST-02, MAC-OP-01 |
macOS host shell, LaunchAgent, TCC onboarding, app discovery, install/repair/uninstall, notarization, update rollback, diagnostics, SBOM. |
180.C.27.01-180.C.27.18 |
MAC-HOST-01, MAC-OP-01; optional Windows/Linux rigs where host claims exist |
Key rotation/revocation, local deny rules, project-root enforcement, consent capture, watermarking, retention/erasure, tamper checks. |
180.C.28.04-180.C.28.13 |
MAC-HOST-01, MAC-OP-01, CLOUD-HETZNER-01 or CLOUD-AWS-01, NET-IMPAIR-01 |
Replay bundles, degraded modes, crash/restart chaos, webhooks/ticketing, SLO evidence, support/export behavior. |
180.C.29.02, 180.C.29.07-180.C.29.16 |
All MVP rigs: MAC-OP-01, MAC-HOST-01, LAN-GW-01, one cloud rig, browser channels |
Final docs and acceptance scenarios: two-Mac LAN, cloud-agent, Blender edit, browser workflow, desktop fallback, Unreal edit, artifact flow. |
180.C.30.01-180.C.30.12 |
MAC-HOST-01, MAC-HOST-02, MAC-OP-01; add Windows/Linux rigs after stages 180.C.36/180.C.37 |
Fleet scheduling, multi-host sessions, locks, render/build queues, fleet health, voice/mobile observer, red-team tests. |
180.C.31 UI foundation items |
MAC-OP-01, MOBILE-IOS-01, MOBILE-ANDROID-01 |
Accessibility, reduced motion, high contrast, RTL layout, keyboard navigation, notifications, cost display, error/loading states. |
180.C.32 adapter SDK/conformance |
At least MAC-HOST-01; add WIN-HOST-01, LINUX-RENDER-01 before claiming cross-platform conformance |
Adapter SDK examples, conformance suite, hot reload, policy sandbox, telemetry hooks, signing/distribution evidence. |
180.C.33 media pipeline |
MAC-HOST-02, MAC-OP-01, LINUX-RENDER-01 when Linux render/audio is claimed |
Timecode, OCIO/ACES metadata, audio capture, HDR capture, DAW/video editor query, color verification tests. |
180.C.34 notifications/sinks |
MAC-OP-01, MOBILE-IOS-01, MOBILE-ANDROID-01, one cloud rig |
Webhook retry, Slack/email/mobile push/PagerDuty/Linear/Jira/calendar notification evidence. |
180.C.35 Tier-2 DCC onboarding |
OS and app-specific rigs added per adapter; minimum MAC-HOST-01 until provider declares otherwise |
Maya/Houdini/C4D/Substance/Nuke/Resolve/Figma/Photoshop/After Effects conformance evidence with rollback/audit parity. |
180.C.36 Windows Host Support |
WIN-HOST-01, WIN-VM-01, MAC-OP-01, one cloud rig |
Signed MSI, Windows Service, DXGI capture, UAC/Defender/SmartScreen, Edge/Chrome CDP, Blender/Unreal discovery, update rollback. |
180.C.37 Linux Host Support |
LINUX-RENDER-01, LINUX-VM-01, MAC-OP-01, one cloud rig |
Signed deb/rpm/AppImage, systemd user units, Wayland/X11 limitations, PipeWire audio, PolicyKit/AppArmor/SELinux, headless DCC roles. |
180.C.38 bridge coexistence/deprecation |
MAC-HOST-01; add old bridge local fixtures |
Old bridge plus Remote Host coexistence, conflict detection, migration docs, telemetry, post-removal verification. |
Minimum MVP Rig Set#
The smallest acceptable MVP hardware budget is:
MAC-OP-01MAC-HOST-01LAN-GW-01or a documented local gateway mode onMAC-OP-01- One cloud rig:
CLOUD-HETZNER-01orCLOUD-AWS-01 NET-IMPAIR-01for network impairment evidence
This minimum set can sign off the macOS-first MVP only. It cannot sign off Windows, Linux, mobile approval, production fleet, or cross-platform adapter conformance claims.
Deferred Expansion Rig Set#
Before checking Windows, Linux, mobile, or production fleet stages, add:
WIN-HOST-01andWIN-VM-01LINUX-RENDER-01andLINUX-VM-01MOBILE-IOS-01andMOBILE-ANDROID-01MAC-HOST-02for advanced media and newer DCC/OS candidates
Evidence Artifact Naming#
Future task evidence should use stable names:
docs/domains/bellona/extras/remote-control/evidence/<item-id>/<date>-<rig-id>-<scenario>.<ext>
Examples:
docs/domains/bellona/extras/remote-control/evidence/180.C.09.07/2026-05-02-MAC-HOST-01-blender-scene-info.mddocs/domains/bellona/extras/remote-control/evidence/180.C.25.04/2026-05-12-CLOUD-HETZNER-01-turn-relay.mddocs/domains/bellona/extras/remote-control/evidence/180.C.36.02/2026-06-03-WIN-HOST-01-dxgi-capture.md
Large binary screenshots, videos, traces, and logs should be registered as
artifacts in the audit/artifact store once 180.C.08 and 180.C.22 exist. The
Markdown evidence file should link to those artifact IDs instead of committing
large binaries to the repo.
Open Inventory Actions#
- Assign owners and physical asset identifiers for every required rig before the first hardware smoke task is checked.
- Decide whether
LAN-GW-01is a separate machine or a role onMAC-OP-01for the MVP. - Choose the first cloud provider rig used for MVP evidence: Hetzner or AWS.
- Confirm exact Blender and Unreal installation paths on
MAC-HOST-01. - Add Windows and Linux rig procurement/setup tasks before
180.C.36and180.C.37begin.