Eve library

Control Room Operator Workflow For Blender And Browser MVP

Guide

Revision 1

On this page

Workflow date: 2026-04-22

Scope: 180.C.12.09

This guide tells an operator how to watch the current Phase 180 MVP command flows for Blender and browser automation from the Bellona Control Room context. It deliberately separates what is live today from what is still fixture-backed.

The current Control Room app shows the operator surface for paired devices, timeline states, approval decisions, stream placeholder/WebRTC controls, and selected-item inspectors. Live Blender and browser command execution evidence is still produced by the committed remote-host CLI smokes. A later item, 180.C.12.10, is the checkpoint for observing command progress and approve/deny decisions through the UI end to end.

Current Support Matrix#

Area Current support
Control Room route Gated /control-room route in apps/bellona/control-room, disabled by default.
Device roster Fixture-backed paired devices, online/degraded state, adapter health, active session state, and permission gaps.
Timeline Fixture-backed queued, started, progress, completed, failed, denied, and approval-required command states.
Approval queue Fixture-backed approve once, deny, timeout, and policy explanation behavior.
Stream Fixture-backed Blender viewport descriptor, screenshot fallback controls, and browser WebRTC loopback probe for one source.
Blender read-only MVP Live or fixture-backed CLI smoke for blender.scene.info through gateway, outbound host, adapter routing, timeline, and audit.
Blender mutation MVP Live-addon optional or deterministic CLI smoke for blender.object.create_primitive with evidence refs and rollback metadata.
Browser MVP Live or mocked CLI smoke for isolated managed browser launch, navigate, snapshot, screenshot artifact, close, and cleanup.
Live UI subscription Not implemented yet. Do not treat the Control Room fixture timeline as live gateway state until 180.C.12.10 closes that path.

Operator Roles#

  • MAC-OP-01: operator machine. Runs the Control Room and, for two-MacBook development, the gateway.
  • MAC-HOST-01: controlled host. Runs the Remote Host, Blender, the Blender addon, and browser automation when live hardware is available.
  • Agent or CLI terminal: starts the smoke command and prints the current live evidence payload.

Safety Boundaries#

Keep these boundaries in place while watching the MVP flows:

  • Do not expose Blender, the Blender addon, Chrome CDP, or the Remote Host health server directly to LAN or internet.
  • Blender addon traffic stays loopback-only on the controlled host.
  • Browser automation uses Bellona-managed isolated profiles only; personal browser profiles remain blocked.
  • Browser CDP stays bound to 127.0.0.1.
  • Mutating browser commands must carry compensating-action metadata. In the current MVP, browser.launch_managed is compensated by browser.close.
  • blender.object.create_primitive is the only safe-mutation Blender command closed by 180.C.10; broad Blender Python, arbitrary file writes, and Unreal console access remain blocked.
  • The Control Room stream is not proof of live Blender or browser pixels yet. Use CLI artifact IDs and smoke output for current live evidence.

Start The Control Room#

From the repository root on the operator machine:

bash
VITE_BELLONA_CONTROL_ROOM_ENABLED=true pnpm nx serve @bellona/control-room

Open:

text
http://127.0.0.1:5182/control-room

Expected operator checks:

  1. Device roster shows the paired Studio MacBook fixture and the degraded Render Mac Studio fixture.
  2. Timeline view shows queued, started, progress, completed, failed, denied, and approval-required rows.
  3. Approval view lets the operator exercise approve once, deny, and timeout on the fixture approval request.
  4. Review view keeps command progress, approve/deny controls, decision outcome, and screenshot-first stream status visible in one workflow.
  5. Stream view shows the Blender viewport source, screenshot fallback controls, and WebRTC direct-loopback status.

These checks verify the operator surface and the expected review vocabulary. They do not prove that the Control Room is receiving the live CLI smoke output.

Watch A Blender Read-Only Command#

Use this when the agent is proving read-only Blender scene inspection:

bash
pnpm nx blender:scene-info-remote-smoke @bellona/remote-host

When a live Blender addon is running on the host loopback endpoint and fallback is not acceptable, require the live addon:

bash
pnpm nx blender:scene-info-remote-smoke @bellona/remote-host -- --require-live-addon

Operator watch points:

  1. Keep the Control Room Timeline tab open and use it as the expected state sequence: queued, started, progress, completed or failed.
  2. Watch the CLI output for status: "passed".
  3. Confirm the command id is command:blender-scene-info-remote-smoke-001.
  4. Confirm auditEntryTypes includes command.received, command.dispatched, and command.completed.
  5. Confirm timelineEvents includes command-store progress and result events.
  6. If --require-live-addon was used, confirm fallback is false.
  7. If fallback is true during a live-hardware run, treat that as evidence that the Blender addon path was not reached.

If the command fails, use the Control Room device roster vocabulary to triage: adapter unavailable, host not connected, missing permission, or command failure. The CLI output is still the source of truth for the current live error.

Watch A Blender Safe-Mutation Command#

Use this when the agent is proving the one closed safe mutation:

bash
pnpm nx blender:create-primitive-remote-smoke @bellona/remote-host

To route through a live local addon instead of the deterministic provider:

bash
pnpm nx blender:create-primitive-remote-smoke @bellona/remote-host -- --live-addon

Operator watch points:

  1. Keep the Control Room Timeline tab open and compare the CLI command lifecycle to the expected queued, started, progress, and completed states.
  2. Watch for timelineResult.resultStatus: "succeeded".
  3. Confirm auditEntryTypes includes command.received, command.dispatched, and command.completed.
  4. Confirm mutationResult.objectId and mutationResult.sceneInfoObjectId name the newly created primitive.
  5. Confirm mutationResult.undoCheckpointId is populated.
  6. Confirm mutationResult.evidenceReferenceCount is greater than zero.
  7. For live-addon runs, confirm the operator can identify the created object in Blender before attempting any rollback.

Rollback is manual in the current MVP. Follow blender-primitive-rollback-and-undo.md for the undo-stack procedure and attach the rollback note shape from that doc to the command review record.

Watch A Browser Managed-Profile Command#

Use this when the agent is proving the Browser CDP MVP:

bash
pnpm nx browser:managed-remote-smoke @bellona/remote-host

For CI-style validation without launching a real browser:

bash
pnpm nx browser:managed-remote-smoke @bellona/remote-host -- --mock-browser

Operator watch points:

  1. Keep the Control Room Timeline tab open and compare the CLI lifecycle to the expected command states.
  2. Confirm mode is live-browser for hardware/browser evidence or mock-browser for deterministic CI evidence.
  3. Confirm browserSession.profileMode is isolated.
  4. Confirm browserSession.cdpHost is 127.0.0.1.
  5. Confirm navigation reaches the expected URL and snapshot.title is present.
  6. Confirm the screenshot output includes artifactId, evidenceId, sha256, and redactionStatus.
  7. Confirm artifactTimelineEvents includes the registered screenshot artifact.
  8. Confirm cleanup.profileRemoved is true after browser.close.

If cleanup fails, do not continue using the profile. Treat the managed profile directory as sensitive evidence, retain the CLI output, and remove the managed directory only after recording the failure.

What The Operator Should Record#

For each Blender or browser run, record:

  • repository commit
  • command invoked
  • operator machine and host machine identifiers
  • whether the run used live hardware or fixture/mock fallback
  • command id
  • terminal status
  • audit entry types
  • timeline event types
  • evidence artifact ids
  • approval decision, if the run required one
  • rollback or compensating-action note for mutating commands
  • any gap between the Control Room fixture state and the live CLI evidence

Current Stop Conditions#

Stop the run and preserve evidence when any of these occur:

  • the host reports a device id that the operator does not recognize
  • the command asks for arbitrary shell, arbitrary Blender Python, real browser profile access, Unreal console access, or desktop input outside the documented approval path
  • Blender addon endpoint is bound to anything other than loopback
  • browser CDP is bound to anything other than 127.0.0.1
  • screenshot artifacts contain sensitive data without a redaction note
  • mutation output has no undo checkpoint or evidence references
  • browser launch or close lacks compensating-action metadata
  • managed browser profile cleanup fails
  • the live CLI evidence contradicts the Control Room fixture state

Handoff To 180.C.12.10#

This workflow is complete for 180.C.12.09 because an operator now has a single documented procedure for watching the current Blender and browser MVP commands from the Control Room context.

180.C.12.10 adds the combined Control Room review workspace and gateway approval HTTP endpoints. That closes the UI-level observe/approve/deny checkpoint for this stage, while live Blender and browser command proof still comes from the CLI smokes until later gateway-to-Control-Room subscription work replaces fixture command rows with live session data.