> For the complete documentation index, see [llms.txt](https://repo.cpsdrone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://repo.cpsdrone.com/auv/introduction.md). # Introduction {% hint style="warning" %} Following files are for non-commercial use only. We offer commercial licenses on [this page here](https://sites.gitbook.com/preview/site_wSbBS/commercial-licenses/). {% endhint %} Our Autonomous submarine (also called the CPS A) is our attempt to **build a fully autonomous underwater vehicle (AUV).** We build it in the Autonomous Submarine Series on our Youtube channel. Link to the series: {% embed url="" %} **Purpose of the autonomous sub:** > 1. *To explore the sea bottom in search of shipwrecks and lost cities.* > 2. *Take our very own picture of the Titanic.* **In other words**: Fly close to the sea bottom, with maximum position accuracy. Use various sensors, like side-scan sonars & cameras for sensing and documenting sea bottom. The vehicle should be fully autonomous, and follow a pre-programmed path without any input from the operator. We eventually plan to **improve the submarine, so that it can film the Titanic**. We're improving our --- # 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://repo.cpsdrone.com/auv/introduction.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.