Model approval is not execution authorization.

The stale-approval failure mode

A model may remain approved while a robot configuration changes, an incident triggers revocation, or the requested action falls outside the reviewed workflow. Treating approval as permanent execution permission loses those contextual checks.

Two-stage design

• Store approval against an immutable release content hash.
• Issue an execution permit only while the release remains approved and not revoked.
• Bind the permit to action hash, device, controller configuration, and a short expiry.
• Consume the permit once at the local gateway and record the result.

Example

A picking policy can be approved as an artifact. A permit for robot A with gripper configuration X must not authorize robot B, configuration Y, or a later action. The local check converts that distinction into an enforceable boundary.

Separate Hosted approval from local evaluation

The stable reference pairs the robot-side runtime with Hosted Cloud and requires independent approval of the exact release. The separate local evaluation prerelease uses an explicitly reviewed local approval file. That local file is not a Hosted login, an independently authenticated reviewer or a permit to move a robot.

For either path, keep the original approval when demonstrating a mismatch or revocation. Record which authority source was used so a reader can interpret the result correctly.

Operational boundary

Authorization constrains when approved content can reach a controller. It does not validate task safety, perception quality, collision avoidance, or the physical environment.

Sources and verification scope

Source code and guides describe implementation and setup. Release notes identify reported checks and their limits. Publication alone does not establish customer use or physical-robot validation.

• Stable runtime approval and execution architecture
• Local prerelease configuration and approval scope

Continue with the relevant guide

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