> For the complete documentation index, see [llms.txt](https://acme-robotics.gitbook.io/road-runner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://acme-robotics.gitbook.io/road-runner/tour/introduction.md). # Introduction Robots are equipped with all sorts of actuators and mechanisms that require software to operate. While human teleoperation may be adequate in some situations, partial or full automation can dramatically improve performance in many situations. For this purpose, Road Runner provides robust solutions for motion planning and execution. In this tour, you will learn simultaneously about Road Runner and the techniques and algorithms behind it. While you may not use all of these components directly, it is imperative to at least have a high-level understanding of what's going on under the hood. The complexity of Road Runner can present pitfalls for beginning users, and debugging is near impossible without general intuition about the system. I've attempted to minimize the math in the tour, but it is occasionally necessary to make the explanations precise. If you'd like to delve even further into the details, check out the resources on [this page](/road-runner/advanced/resources.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://acme-robotics.gitbook.io/road-runner/tour/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.