RLSOK
Shadow Evaluation

Evaluate one learned-policy release before connecting hardware.

Run one learned policy through RLSOK in a simulated ROS 2 workflow, record eligible and blocked decisions, and identify the practical integration requirements for your controller path.

Download and try RLSOK
01

Start on your own

You can download RLSOK and run the local example without an application, a robot, ROS or a cloud account. Follow the download page for supported systems. Cloud account creation is also self-service. The assisted evaluation below is optional help for a specific integration, not a condition of product access.

02

Who it is for

  • Robotics teams moving learned or autonomous policies from simulation into ROS 2 deployment workflows.
  • Teams managing multiple artifacts or configurations that need reproducible release identity.
  • Teams that need approval, revocation, expiry, and inspectable release decisions before hardware connection.
  • Not every ROS 2 project needs this release-control boundary.
03

Optional assisted evaluation

  • If you want hands-on help, contact us to discuss the setup. Downloading and trying RLSOK does not require this discussion.
  • Select one representative learned policy.
  • Identify the model-to-controller path.
  • Define the release bindings.
  • Run eligible and blocked cases in Shadow Mode; controller dispatch is not attempted.
  • Record the release-decision Evidence.
  • Identify approval, identity, expiry, revocation, and rollback gaps.
  • Decide whether to develop a reference integration.
04

Expected outputs

  • A release-boundary map.
  • The recommended RLSOK integration point.
  • One represented executable release.
  • An example eligible decision.
  • An example blocked decision.
  • An Evidence record.
  • Documented integration requirements.
  • A reference-integration recommendation.
05

What RLSOK provides

  • Release-control architecture review.
  • Representation guidance.
  • Shadow Mode evaluation.
  • Release-decision Evidence.
  • Integration-gap documentation.
06

What the design partner provides

  • One representative learned policy.
  • Non-secret artifact metadata or a safe test artifact.
  • ROS 2 distribution and environment details.
  • A robot/controller interface description; RLSOK does not currently implement an ActionContract schema.
  • Representative eligible and blocked cases.
  • Technical feedback and explicit permission before anything is published.
07

First-phase boundary

Neither party is required to connect physical hardware during the first phase. The evaluation does not promise certification, production readiness, guaranteed integration, safety, free engineering work, or a public collaboration.

Frequently asked questions

Do we need to connect a real robot?

No. The Shadow Evaluation begins with one policy in a simulated ROS 2 workflow, and controller dispatch is not attempted.

Does the evaluation certify a deployment as safe?

No. It identifies release-control assumptions and gaps; it is not a certification, compliance assessment, or functional-safety evaluation.

Can it cover an existing model registry?

Yes. The discussion can start at your current registry or artifact store and trace the bindings through local ROS 2 dispatch.

Continue with the relevant guide

ROS 2 Shadow ModePolicy approval workflowRLSOK architecture

Try the local example without an application. For setup or integration help, you can also contact us.