> For the complete documentation index, see [llms.txt](https://docs.havl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.havl.io/products/havl-motion.md). # havl motion **havl motion** extends the human verification layer to robotics, autonomous machines and embodied AI. It enables autonomous systems to request human judgment when perception, planning or execution reaches a situation that cannot be handled with sufficient confidence. Instead of relying on continuous remote operation, humans become involved selectively — when the machine encounters an exception, uncertainty or predefined safety boundary. **Machines move. Humans intervene when it matters.** ### Human judgment for the physical world Robots operate in environments that are significantly less predictable than purely digital systems. People move. Objects change position. Visibility deteriorates. Sensors disagree. Infrastructure differs. Unexpected obstacles appear. Situations occur that were rare or absent in training data. An autonomous system may perform thousands of routine actions correctly and still encounter a situation where proceeding automatically is not the appropriate response. havl motion creates a way for the machine to request external human judgment at those moments. The system remains autonomous during normal operation. When uncertainty or a predefined condition is detected, the relevant sensor information, context and possible actions can be routed to a human verifier. ### Where can humans be involved? havl motion can support different points within an autonomous system. Typical use cases include: * visual scene confirmation * object or obstacle identification * ambiguous environmental conditions * action selection * route or movement confirmation * exception handling * safety escalation * conflicting sensor information * unusual physical-world situations * remote expert judgment Clients determine which situations require human involvement and what information should be presented to the verifier. This allows human oversight to focus on the edge cases where automated systems have the greatest uncertainty. ### Perception verification Before a machine decides what to do, it first needs to understand its environment. Computer vision and sensor systems can encounter ambiguous situations caused by poor visibility, unfamiliar objects, occlusion, unusual environments or conflicting sensor data. havl motion can route these situations to humans for independent confirmation. A verifier might determine whether an object is present, classify an unknown obstacle, compare competing interpretations or confirm whether the machine's perception of a scene is reasonable. The verified result can then be returned to the autonomous system as additional information for its next decision. ### Action selection Sometimes the environment is understood, but the appropriate action is uncertain. An autonomous machine may have several possible responses and insufficient confidence to select between them. In these situations, havl motion can present the available context and proposed actions to a human. Depending on the configuration, the verifier can select an action, approve a proposed action, reject it, provide additional information or escalate the situation. The machine can then continue according to the verified decision and its own operating constraints. ### Exception handling Autonomous systems are generally optimized for expected operating conditions. The difficult cases are the exceptions. A delivery robot encounters an unexpected construction site.\ An industrial robot detects an unfamiliar object in its workspace.\ An autonomous inspection system finds something it cannot confidently classify.\ A machine reaches a situation outside its normal operating parameters. Rather than forcing the system to choose between proceeding autonomously and stopping indefinitely, havl motion provides another option: **ask a human.** The exception can be routed to an appropriate verifier and the machine can continue once the required judgment has been provided. ### Risk-based intervention Human involvement can be proportional to the potential impact of the machine's next action. Routine situations can remain fully autonomous. Uncertain but low-risk situations might require confirmation from a single verifier. More consequential situations can require multiple independent decisions, stronger consensus or escalation to a **Certified Expert** with relevant domain knowledge. Clients define these requirements according to their system, operating environment and risk model. This allows human oversight to become more rigorous as the consequences of an incorrect autonomous decision increase. ### Humans for the edge cases havl motion is not designed to turn autonomous machines into remotely operated machines. Continuous teleoperation would remove much of the benefit of autonomy and would not scale efficiently across large fleets. Instead, havl motion follows a different model: **machines handle the routine; humans handle the exceptions.** A robot may complete hundreds or thousands of actions independently before requesting human assistance. As autonomous systems improve, the percentage of situations requiring intervention may continue to decrease. But the remaining edge cases can also be some of the most difficult and consequential. havl provides a scalable human layer for those moments. ### From digital autonomy to physical autonomy AI is moving beyond screens and software. Autonomous systems increasingly perceive environments, make decisions and perform actions in the physical world. That makes the consequences of uncertainty different. An incorrect generated answer can be corrected. An incorrect physical action may be significantly harder to reverse. havl motion brings independent human judgment into that final layer of autonomy — selectively, remotely and only when needed. **Machines act. Humans verify.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.havl.io/products/havl-motion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.