# Relationship with PUAI

Pumpad introduces a **dual-token architecture**, designed to separate long-term governance power (PUAD) from rapid utility consumption (PUAI). This model ensures transparency, scalability, and balance between growth and sustainability.

| Functional Layer | PUAD (Platform Governance Token)           | PUAI (AI Consumption Token)                   |
| ---------------- | ------------------------------------------ | --------------------------------------------- |
| Core Role        | Utility, permissions, identity, governance | AI engine access, task execution, burn-on-use |
| Token Nature     | Long-term holding, carries governance      | Disposable, no voting rights, short-lived     |
| Supply Model     | Fixed: 1B PUAD                             | Elastic: mint-to-burn                         |
| Burn Mechanism   | Not designed for regular burning           | Auto-burned on each AI/task interaction       |
| Pricing Model    | Market-based + DAO adjusted                | Usage-driven, dynamic pricing                 |
| Access Rights    | Unlocks features, plugins, identities      | Executes real-time AI and mission logic       |

***

**🔁 Coordinated Interaction**

1. **PUAD unlocks access** to premium modules, AI plugin dashboards, and mission tooling.
2. **PUAI fuels real-time use** — every AI call (text generation, task logic, model activation) consumes PUAI.
3. **Incentives are hybridized** — high-volume plugin devs can earn both PUAD (platform rewards) and PUAI (usage revenue).
4. **Future conversion layer** between PUAD → PUAI will allow temporary balance top-up without friction.

***

**✅ Model Advantages**

* Lowers operational friction for AI services
* Prevents platform token dilution via high-frequency use
* Creates **clear economic signaling**: PUAD = rights, PUAI = fuel
* Enables parallel growth of governance layer and consumption engine


---

# 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://pumpad.gitbook.io/pumpad/relationship-with-puai.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.