> For the complete documentation index, see [llms.txt](https://docs.stormrae.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stormrae.ai/waitlist/guilds-and-badges.md).

# Guilds & Badges

#### Guild classifications

Architects are foundation builders who designed the participation layer.

Shapers are early contributors who refined adversarial testing.

Pioneers are explorers who pushed security boundaries.

Guardians are defenders protecting AI integrity.

Sentinels are watchful contributors scanning for vulnerabilities.

Seekers are newcomers searching for vulnerabilities.

Your badge is permanent. It shows you were here early. Your guild is determined by when you joined the waitlist. Earlier arrival means higher rank and more starting shards.

| Position        | Guild      | Starting Shards |
| --------------- | ---------- | --------------- |
| 1 to 2,000      | Architects | 1,000           |
| 2,001 to 4,000  | Shapers    | 750             |
| 4,001 to 6,000  | Pioneers   | 500             |
| 6,001 to 8,000  | Guardians  | 300             |
| 8,001 to 10,000 | Sentinels  | 150             |
| 10,001+         | Seekers    | 50              |


---

# 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://docs.stormrae.ai/waitlist/guilds-and-badges.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.