> For the complete documentation index, see [llms.txt](https://rocketry.gitbook.io/public/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rocketry.gitbook.io/public/reference/high-power-rocketry-hpr/hpr-certification.md).

# STAR HPR Certification

Some of the members listed below may no longer be with the team, but they are often available to help out in the #rocket-design channel!

| Name                  | Organization and Certification Level |
| --------------------- | ------------------------------------ |
| Michael Celebrado     | TRA L2                               |
| Aled Cuda             | TRA L2                               |
| Elizabeth Gammariello | NAR L1                               |
| Rajiv Govindjee       | NAR L1                               |
| Ilyas Kamil           | NAR L2                               |
| Sean Pak              | NAR L1                               |
| Jacob Posner          | NAR L1                               |
| Aaron Togelang        | NAR L1                               |
| Jenya Pryadkin        | TRA L2                               |


---

# 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://rocketry.gitbook.io/public/reference/high-power-rocketry-hpr/hpr-certification.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.