oss-solution-registry-onboard

To onboard an open-source robotics repository into the NPA registry, you must complete capability discovery, containerized build verification, and successful execution of end-to-end smoke tests on Nebius infrastructure. This ensures only verified, testable solutions are admitted to the catalog.

Physical AI solution validation is the process of evaluating robotics, simulation, and policy-training repositories for Workbench integration through live infrastructure smoke testing. It is required when promoting a raw GitHub repository to a fully documented, registry-ready NPA solution.

Yes, onboarding a simulation repository requires mandatory live infrastructure smoke testing on Nebius infrastructure. This validation enforces build, pull, and execution success to guarantee that the open-source solution is testable and high-quality before registry admission.

You document upstream capabilities by systematically identifying and describing them using the project's own native vocabulary. This strict adherence to documented capabilities ensures accurate workflow specs and standardized onboarding into the NPA registry.

Yes, you can use this validation process for policy-training repositories alongside robotics and simulation projects. The skill evaluates these repositories for Workbench integration by verifying containerized builds and executing end-to-end smoke tests on Nebius infrastructure.

Repository onboarding requires containerized build verification to enforce strict build and execution success before admission. This live infrastructure validation step ensures that raw GitHub repositories meet the standardized quality and testability criteria of the NPA catalog.