> For the complete documentation index, see [llms.txt](https://lore.chainrunners.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lore.chainrunners.xyz/trait-lore/pyramid-hat.md).
# Pyramid Hat
Originally an ill-advised design by a low-paid intern at JANK Street, the pyramid hat, as it's officially known, was originally an attempt to make a statement about an illuminati that could not see. The design was inexplicably released into JANK's catalog, failed to sell, and the intern was subsequently fired.
The discarded unsold inventory was eventually commandeered by a dangerous, unpredictable group of shadowy info brokers, gamblers, and financial advisors known for huddling in the depths of the infamous Alpha Vault. Identifying an unintended synergy between the pyramid design and the shape of the world's largest potato chip corporation's flagship product, the hat became a favorite symbol of the Vault, and is now known more commonly among runners as the "chip hat".
Vault dwellers continue to bring awareness to the extraordinary public demand which exists for the referenced potato chip corporation to enter into a promotional partnership with the Vault, in tribute for their unsolicited brand propagation.
**Associated Brand:** JANK Street
---
# 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://lore.chainrunners.xyz/trait-lore/pyramid-hat.md?ask=&goal=
```
`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.