> For the complete documentation index, see [llms.txt](https://plants.cometrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plants.cometrobotics.org/miscellaneous/robot-ownership-for-club-funded-bots.md).

# Robot Ownership for Club Funded Bots

In general, any parts paid for by Comet Robotics remain under the ownership of  the club. Club members are able to loan parts owned by the club for use in their own robots. These parts will count against your budget.

All members are allowed to work on a Plastic Ant-weight (Plant) project individually. They will be supplied filament for 3D printing and a standardized set of electronics to use in their Plant.

To build a full combat robot, any member must meet these requirements;

* Must have built a Plant
* Must have competed in at least 3 separate events with the same Plant
* Must iterate and improve the design of the Plant between events

After completing these requirements they can begin to work on a full combat robot. They will not be given any funding for the bot until the design passes a design review check by the Combat Officers. Full Combat Ants(1lb) will be given $250 for their budget, Beetles(3lb) will be given $550 for their budget, and Hobbies(12lb) will be given $1000.

Ants can be worked on individually, Beetles require a team of at least 2 people, Hobbies require a team of at least 2 people. The club will try to provide funding for 4 Ants and 2 Beetles per semester and 1 Hobby per academic year.

Club members can purchase parts from the club at the price they were originally bought at, and those parts are now owned by the member.&#x20;

When a bot retires, one copy of the shell goes to the club member and one copy of the shell goes to the club to put on display. All the electronic parts will be removed from the retired bot and returned to the clubs inventory of parts for future bots to use.


---

# 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://plants.cometrobotics.org/miscellaneous/robot-ownership-for-club-funded-bots.md?ask=<question>&goal=<user_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.
