Interactive labs

Workspace Control Center

This blueprint tracks the browser-based IDE, hardware bridge, AI copilot, and mission system required for ROS, ROS2, micro-ROS, MicroPython, FPGA, and RTOS workflows. We ship each phase with the same operational rigor as the ledger stack—shared helpers, JSONL logs, and `/admin/ops` visibility.

Guiding principles

  • Every workspace is reproducible: container image + mission manifest + AI action log.
  • Hardware access is auditable: flashing, telemetry captures, and RTOS builds emit JSONL events tied to payouts.
  • The tutor stays accountable: recommendations require human confirmation and stream to `/admin/ops` alongside ledger health.

Phase 1

Workspace Fabric

Launch browser IDEs + containers for every mission.

In progress

Provision per-user containers (Docker/Firecracker) with Node, Python, ROS, FPGA, and RTOS toolchains pre-installed. Stream terminals + file edits directly into the browser UI.

  • In progress

    Container images

    Base + ROS/micro-ROS + FPGA variants published to registry.

  • Planned

    Browser IDE shell

    Expose VS Code Web + multiplexed bash/PowerShell sessions per learner.

  • Planned

    State sync

    Persist workspaces via Supabase buckets + JSONL run logs.

Phase 2

AI Copilot Control

Bind the AI tutor to workspace files, commands, and tests.

Planned

Extend /api/ai endpoints so copilots can inspect repos, propose diffs, run tests, and summarize failures with audit trails.

Depends on: Phase 1

  • Planned

    Workspace context feed

    Secure channel streaming file trees + terminal output to the tutor.

  • Planned

    Command broker

    API for tutor-issued workspace.exec requests with human approval gates.

  • Planned

    Action ledger

    Log every AI intervention to JSONL for review + payouts.

Phase 3

Hardware & Lab Agent

Bridge microcontrollers, FPGAs, and instruments into the browser.

Planned

Ship a lightweight agent that exposes WebUSB/WebSerial, JTAG, oscilloscope, and logic-analyzer feeds back to the workspace UI and AI tutor.

Depends on: Phase 1

  • Planned

    Device discovery

    Detect Arduino, ESP32, STM32, FPGA boards, and RTOS targets via USB.

  • Planned

    Flashing + telemetry

    Provide safe firmware flashing with automatic log capture + rollback.

  • Planned

    Virtual instruments

    Render scope/logic data in-browser when physical gear unavailable.

Phase 4

Mission System

Package ROS/RTOS/MicroPython projects with auto grading + payouts.

Planned

Mission manifests define repo templates, BOMs, checkpoints, and payout triggers so every build log ties into the ledger.

Depends on: Phase 1 → Phase 2 → Phase 3

  • Planned

    Manifest schema

    Describe hardware kits, datasets, and test harness per mission.

  • Planned

    Test adapters

    Support Jest, rostest, Zephyr, MicroPython, Verilator harnesses.

  • Planned

    Ledger hooks

    Emit mission-complete events so payouts + ops dashboards stay in sync.

Course coverage

Workspace-to-course matrix

Verify every stack ships with active missions, telemetry tags, and manifest IDs before opening labs.

9 total courses

Base IDE

Node/Python, pnpm, AI builder stack

6 tracks

ROS Ops

ROS 2 Humble, Gazebo, micro-ROS bridges

Needs coverage

No courses wired to this workspace yet. Attach mission manifests + telemetry tags before launch.

Embedded Fabric

Zephyr, ESP-IDF, PlatformIO, flashing toolchains

2 tracks

FPGA & Neuromorphic

Yosys, nextpnr, Verilator, openFPGALoader

1 tracks

Workspace instances

Local JSONL-backed records that simulate the orchestrator until real containers ship.

Running

0

Live containers

Provisioning

0

Booting

Stopped

0

Archived

Next expiry

No active TTL

WorkspaceImageMissionStatusCreatedExpiresRuntime / LogsActions
Loading workspace records…
PowerProgress