> For the complete documentation index, see [llms.txt](https://robodex.gitbook.io/robodex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robodex.gitbook.io/robodex-docs/pipeline/cad-procurement.md).

# CAD And Procurement

CAD and procurement helpers live under:

```
packages/pipeline/cad/
packages/pipeline/components/
packages/pipeline/procurement/
```

## CAD assembly

CAD helpers translate robot body data into printable or inspectable part structures.

Relevant files include:

* `cad/assembly_builder.py`,
* `cad/cadquery_parts.py`,
* `cad/print_export.py`.

## Print export

The product print export route writes files under:

```
data/exports/{design_id}
```

This export path should be treated as artifact generation from stored designs, not as a new body-generation algorithm.

## Component slots

Component-slot code maps design needs to physical parts or placeholders.

Examples:

* actuator slot requirements,
* sensor slot requirements,
* contact hardware,
* structural components.

## Procurement reports

Procurement code can produce reports describing the components needed for a design. This is useful for bridging generated robot concepts into build planning.

## Current maturity

CAD and procurement are downstream from generation. They depend on the quality and completeness of the generated body representation.

If a candidate only contains flat product fields, export code may need defaults. If it contains richer IR or component data, CAD and procurement can become more faithful.


---

# 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://robodex.gitbook.io/robodex-docs/pipeline/cad-procurement.md?ask=<question>&goal=<endgoal>
```

`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.