Action boundary
G‑14 governs actions like enter zone, launch mission, lift object, release route, start teleop, or actuate equipment.
Robotics and manufacturing
Runtime assurance for machines that move, lift, enter, release, and act.
G‑14 sits above low-level motor control and below mission intent. It governs high-consequence robot and machine actions at the skill, command, route, and safe-state boundary.
Why this buyer cares
Robot safety files and fleet logs help, but adaptive machines need runtime proof for which action was permitted, held, blocked, released, or failed closed.
Action Range scenarioRobot zone entry
Run the scenario to see the control loop before moving into a deployment review.
Run the scenarioSafe-state behavior
Hold, timeout, denial, and evidence failure produce explicit safe-state behavior instead of silent operational ambiguity.
Portable dispute record
Manufacturers, warehouse operators, insurers, and customers can evaluate what was permitted and what evidence survived.
Questions this path answers
- Was the robot action in an authorized envelope?
- Did human release happen where required?
- Did timeout fail closed?
- Can the disputed action record be independently checked?
What the buyer leaves with
- Robot action control model
- AMR proof test path
- Physical AI runtime assurance page
- Industrial evaluation request
Next move
Start with proof, then choose the smallest serious evaluation path.
Bring one action into the range: what can it change, who can release it, what evidence must survive, and what proof the buyer needs if the action is challenged.