| name | architecture |
| description | Use for Claude Code architectural review of the Nebius Physical AI platform, workbench layer, orchestrator choices, and partner model. |
Architecture Context
Detailed rationale and the preserved May 2026 architecture snapshot live in
docs/architecture/contributor-context.md.
The platform progression is:
- Tools: Workbench.
- Composition: Platform.
- Intelligence: agentic layer.
The current phase is Workbench, the Tools layer: marketplace model, pay per use, npa CLI/SDK/agents.
There are 8 tools: LeRobot, FiftyOne, Genesis, Isaac Lab, Cosmos, LanceDB, GR00T, and SONIC.
Tool validation state: 8/8 named Workbench tools have at least one
artifact-bearing e2e validation on Nebius. Cosmos closed the last gap in W13
through cosmos train --runtime serverless --smoke; Cosmos visual-generation
rendering paths remain constrained by the EGL/DRI container gap.
SkyPilot is the sole orchestrator. Argo is deprecated.
Partner model: partners listed in the ecosystem must run workloads on Nebius infrastructure when accessed through the platform.
LeRobot connects data generation to robot policy training and is the default training framework for robot policy workflows.
The sim-to-real gap is the most important and least-tooled layer. Existing approaches are either deeply custom or unproductized.
OSS and container packaging
- OSS onboarding ladder (BYOF → workflow → first-class tool):
docs/architecture/oss-onboarding-ladder.md
- Container packaging tiers and security baseline:
docs/workbench/container-packaging.md
- Machine-readable packaging contract:
npa/docker/workbench/packaging-contract.yaml
- Generic BYOF operator skill:
skills/workflows/byof-onboard/SKILL.md
(npa workbench byof, npa.sdk.workbench.byof, workbench.byof.repo)
