> For the complete documentation index, see [llms.txt](https://doperaider.gitbook.io/doperaider/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doperaider.gitbook.io/doperaider/dirt-lore.md).

# DIRT Lore

DIRT is the second product line in the DopeRaider economy. WEED grows from the street. DIRT is mined from the network.

In fiction, DIRT is stolen private data: leaked credentials, intercepted messages, scraped corporate records, ripped databases, surveillance feeds, identity bundles, and other information dangerous enough to move like contraband. The contents stay abstract on purpose. DopeRaider uses hacker culture as a game world, not as an instruction manual.

## The Duality

| WEED          | DIRT            |
| ------------- | --------------- |
| Grown         | Mined           |
| Organic       | Digital         |
| Street dealer | Hacker operator |
| Grow room     | Server room     |
| Bags          | Dossiers        |
| Green         | Red             |

Same empire. Two fronts.

## The Chain

```
WEED: SEEDS    -> GROWING -> WEED
DIRT: EXPLOITS -> MINING  -> DIRT
```

EXPLOITS are the consumable input for DIRT. They represent fictional black-market access packages, compromised systems, leaked access, and other abstract digital openings. Players burn EXPLOITS to start a MINING cycle and receive DIRT measured in GB.

<figure><img src="/files/5SQxGQUrwSYEvLbCHwrA" alt="EXPLOITS icon" width="140"><figcaption><p>EXPLOITS fuel DIRT mining.</p></figcaption></figure>

<figure><img src="/files/BKH3YWoNZNeaMjEr0L6V" alt="DIRT icon" width="140"><figcaption><p>DIRT is data with a price on it.</p></figcaption></figure>

## What DIRT Represents

DIRT is compromat, also known as kompromat: compromising and blackmail material that is valuable because it can damage reputations, expose secrets, or shift power between crews. It can be leaked messages, private records, surveillance pulls, identity bundles, internal files, compromising media, or any other dangerous information abstracted into a tradeable in-game commodity.

The current contracts and game UI do not implement separate DIRT hardware tiers or capacity classes. DIRT is displayed in GB as a game unit. Carry-capacity upgrades affect how much total inventory a player can move, but they are not a DIRT-specific storage system.

## The Archive

The LockUp is where confiscated street product goes. The DIRT-side mirror is The Archive: a vault of seized data that grows when players are busted carrying DIRT.

The Archive can be treated as:

* a federal server farm
* a cartel data vault
* an abandoned datacenter
* a myth no raider can verify until the jackpot opens

Mechanically, the Archive follows the same jackpot logic as the LockUp: confiscated value accumulates, players can attempt a high-risk raid, and a successful jackpot can overfill capacity until the winner sells down.

## Tone Rules

Use these words freely:

* DIRT
* EXPLOITS
* MINING
* THE ARCHIVE
* ENCRYPTION
* FIREWALL
* MINING POWER
* GB

Avoid real hacking instructions, real victims, real CVEs, or anything that reads like a guide to attack real systems. DIRT is game fiction and economic texture.


---

# 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://doperaider.gitbook.io/doperaider/dirt-lore.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.
