> For the complete documentation index, see [llms.txt](https://docs.hackerfab.org/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackerfab.org/home/working-docs/2d-crystal-stacking-robot-wip/notice.md).

# NOTICE

```
Carnegie Mellon University — Open Source Hardware Lab

All files in this repository are provided under the licences listed below.

Any copies or substantial portions of these files \*\*must retain this NOTICE\*\*.

Carnegie Mellon University is to be noted as an author for all files in this repository.



Hardware design files: CERN Open Hardware Licence v2.0 (Strongly/Weakly Reciprocal)

Software \& firmware:   Apache Licence 2.0   (or: Mozilla Public Licence 2.0)

Documentation:         Creative Commons Attribution-ShareAlike 4.0



Trademark \& endorsement:  

“Carnegie Mellon University”, “CMU”, the CMU seal and Tartan logos are

registered trademarks of Carnegie Mellon University.  These marks \*\*may not be

used in derivative works, marketing materials, or product labelling without

separate written permission from CMU\*\*, and no derivative work may imply

CMU’s endorsement or sponsorship.
```

<br>


---

# 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.hackerfab.org/home/working-docs/2d-crystal-stacking-robot-wip/notice.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.