# The Lore

<mark style="color:purple;">Lore</mark>

The Open Outcry lore is a parody of the NFT space. So many of use have witnessed rugged projects, whether they were intentionally rugged by malicious founders, abandoned by founders that gave up or founders who just failed to execute and drove the value to zero. On top of that you have influencers who pump and dump floors, hackers who send fake links or other mechanisms to drain your wallet and just flat out rude and arrogant people everywhere.&#x20;

Degens and Blur farmers destroy value and the space is littered with the hype project of the day where you see projects with horrible art and no vision get to 1 ETH floors while founders with good art and utility who work around the clock are staring at .02 floors. This space is nuts and we are here to make fun of it with a story that will make you laugh and provide a little "group therapy" along the way.

Another use of the lore from a page from Killabears, is to use it as an interactive and suspenseful mechanism for communicating a real time roadmap. The old method is to publish a long whitepaper with a dream of deliverables. Once it is on paper you are held to every word and every day you hear the chant for "WEN?".

Instead, we will work off a vision and pivot as needed to bring the most possible value we can to our holders. The key is to constantly deliver so that the community has enough trust in leadership that the lore roadmap method is accepted. And deliver is what we intend to do.

In fact, we are not launching this project until our initial utility is complete. Utility on day one is our motto.


---

# Agent Instructions: 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:

```
GET https://open-outcry-nft-wiki.gitbook.io/open-outcry-the-lore/open-outcry-utility/the-lore.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.