> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/design/cad-standards/fusion-file-structure.md).

# Fusion File Structure

As discussed in the Parts of a Robot page, we have multiple different types of things that make up a robot. We have to keep those organized to know what we are working on. The first half of that is acheived by implementing the Design Part Numbering system. The second half of that is acheived by rigorously structuring our Fusion robot assembly folder. This page will walk through the expectations and structure of our Fusion robot assembly.

{% content-ref url="/pages/HF3dBtEabAMquEguuQnM" %}
[Parts of a Robot](https://docs.raidrobotics.org/design/cad-standards/parts-of-a-robot.md)
{% endcontent-ref %}

## Top Level

Each year, a new robot folder will be created. All parts and assemblies for that robot should be in that folder.

<figure><img src="https://3371293148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9qOZFPsH0lfSzbgmM0Zp%2Fuploads%2Fgit-blob-c208e3370f3b788a6aac2281cc95e97583ce424e%2Fimage.png?alt=media" alt="" width="375"><figcaption><p>2025 Robot Assembly Folder</p></figcaption></figure>

Inside the folder, there will be:

1. A top level robot assembly file named 25-00000 (or similar depending on the year)
2. Folders for each subsystem

{% hint style="danger" %}
Nothing except Folders and the top level robot assembly file should be in the top most folder
{% endhint %}

<figure><img src="https://3371293148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9qOZFPsH0lfSzbgmM0Zp%2Fuploads%2Fgit-blob-9777d0d619b4a9001fbffa32b399c1ee923d6d28%2Fimage%20(2).png?alt=media" alt="" width="375"><figcaption><p>Items within 2025 Robot Assembly Folder</p></figcaption></figure>

## Subsystem Folders

Each subsystem will have its own folder labeled with the subsystem number and the subsystem name (ex: 25-01000 Drive Subsystem). Within the respective subsystem folders, parts and assemblies for that subsystem will be stored. There should only be one Fusion file for that subsystem labeled as such (ex: 25-01000 Drive Subsystem) as all other parts need to be stored within assembly folders.

<figure><img src="https://3371293148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9qOZFPsH0lfSzbgmM0Zp%2Fuploads%2Fgit-blob-db033433b5a2e8eca3f3fd90653bcbfce229e206%2Fimage%20(3).png?alt=media" alt="" width="375"><figcaption><p>Items within 25-01000 Drive Subsystem folder</p></figcaption></figure>

## Subsystem Assembly Folders

Each assembly within a subsystem will have its own folder and be named as such (ex: 25-01100 Chassis). There will also be a Fusion file labeled the same. Individual parts that go into the subsystem assembly will also be stored within this folder labeled with their part number and common name (ex: 25-01101 Chassis Left Rail)

{% hint style="warning" %}
Please make sure that when you save parts, they are saved within the correct subsystem assembly folder
{% endhint %}

<figure><img src="https://3371293148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9qOZFPsH0lfSzbgmM0Zp%2Fuploads%2Fgit-blob-5a8dbf87e8c88214e1e8d6398499eb51ffd84aad%2Fimage%20(4).png?alt=media" alt="" width="375"><figcaption><p>Files within 25-01100 Chassis Assembly folder</p></figcaption></figure>

<figure><img src="https://3371293148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9qOZFPsH0lfSzbgmM0Zp%2Fuploads%2Fgit-blob-54f6d2a364075ef3effddac48afba2709a0c684c%2Fimage%20(6).png?alt=media" alt="" width="375"><figcaption><p>Image showing file hierarchy</p></figcaption></figure>


---

# 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.raidrobotics.org/design/cad-standards/fusion-file-structure.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.
