Architecture
Presentation plane
Next.js renders experiments, runs, providers and architecture while delegating mutations to server-side services.
Control plane
The domain orchestrator validates specs, transitions run state, registers artifacts and summarizes results.
Execution plane
Mock TypeScript providers and the Python Simulation Gateway own execution. Future simulator adapters stay behind provider interfaces.
Data plane
Local files are the default. Production uses provider-neutral Postgres metadata and Vercel Blob artifacts.
Vercel boundary
Vercel coordinates complete jobs through durable workflows. It does not drive low-level robot-control steps.
Robotics boundary
The Simulation Gateway owns the inner loop beside the simulator and policy runtime.