# System Map

The Drifters system is designed as a closed economic loop where identity, work, currency, goods, and energy reinforce one another. This map provides a high-level overview of how value circulates within the economy.

***

### **Core Elements**

**Identity (NFTs):**\
NFTs establish citizenship. They define roles, verify ownership, and unlock access to the system.

**Work (Aevitas WU):**\
Citizens perform Work Units in Aevitas. Effort produces Benny, linking digital labor to economic participation.

**Currency (Benny):**\
Benny is the medium of exchange and store of value. It is earned through work and minted through solar output.

**Future Gadgets (Goods):**\
Functional goods including upgrades, consumables, and equipment. They provide utility, expression, and productivity.

**Spacemart (Marketplace):**\
The hub for trading and upgrading Future Gadgets. Spacemart captures fees in Benny and routes value back into the system.

**Energy (Solar, Proof of Stake):**\
Solar production anchors Benny to measurable output. Proof of Stake provides digital security and validation.

**Treasury and Staking:**\
Reserves are managed collectively. Staking distributes yield and strengthens governance weight.

**Governance:**\
Citizens set parameters for emissions, fees, and treasury policy. This ensures long-term alignment and adaptability.

***

### **Flows of Value**

1. Citizens perform work to earn Benny.
2. Benny is used in Spacemart to acquire Future Gadgets; fees and burns reduce supply.
3. Solar output mints Benny and generates fiat revenue for the Treasury.
4. The Treasury expands solar and infrastructure, compounding productive capacity.
5. Governance adjusts parameters, sustaining balance across the system.

***

### **Cycle Summary**

The economy follows a closed loop:

**Citizenship → Work → Currency → Goods → Marketplace → Energy → Treasury → Governance → back to Citizenship.**

Each component strengthens the others, creating compounding growth in both digital and physical dimensions.


---

# 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://driftopia.gitbook.io/whitepaper/system-map.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.