Treat release control as one layer, not the whole safety case.
Learned-policy deployment needs precise artifact identity and authorization, but those controls do not replace hazard analysis, independent protective systems, validation, or trained operational oversight.
Download and try RLSOKWhat release control can address
- Which immutable policy artifact was reviewed.
- Whether the release is approved or revoked.
- Which device and controller configuration may consume authorization.
- What decision and dispatch evidence was recorded.
What remains outside this layer
- Model behavior correctness across the operational domain.
- Safety-rated sensing, stopping, guarding, and emergency functions.
- Site-specific risk assessment and operating procedures.
- Certification or regulatory compliance conclusions.
A practical review
Document the release-control boundary beside the independent safety boundary. Test mismatches, revocation, stale permits, network loss, and unavailable databases in simulation. Keep the robot-side gate unable to silently bypass a denied decision.
Continue with the relevant guide
Try the local example without an application. For setup or integration help, you can also contact us.