# AIR3 Documentation

AIR3 is the public documentation hub for the AIRewardrop ecosystem.

It documents the AIR3 agent experience, AIRdApp product surface, AIRTrack strategy validation, AIRTrading protocol logic, AIR3 token utility, and the operating rules used to provide transparent user-facing products.

## What AIR3 includes

* **AIR3 Agent**: AI-native crypto agent experience across social and community channels.
* **AIRdApp**: product interface where users can access AIR ecosystem modules.
* **AIRTrack**: live tracking and simulation environment used to validate strategies on real market data and social momentum signals.
* **AIRTrading**: real execution layer where strategies may be deployed only after passing live validation on AIRTrack.
* **AIRSocial / AIRSponsor / AIRTool**: utility modules that expand AIR3 usage through community, sponsorship, and agent rental features.
* **AIR3 Token Utility**: buy-and-burn mechanisms, rewards, and ecosystem access flows.

## Core operating principles

### 1) AIRTrack and AIRTrading are not the same product

AIRTrack is a **tracking, simulation, and validation layer**. It models entries and exits, tracks PnL, and records strategy behavior in a live environment. It does **not** execute real trades.

AIRTrading is the **real execution environment**. It is the deployment layer for strategies that have already passed live validation requirements on AIRTrack.

**Strategy lifecycle**\
Idea -> live validation on AIRTrack -> promotion to AIRTrading after passing live tests

### 2) Transparent trade traceability

AIR3 combines **social transparency** and **protocol/accounting transparency**.

* Trade announcements are posted on X at position opening: <https://x.com/AIRewardrop>
* A closing confirmation card is posted when the trade closes, including realized PnL
* AIRdApp and AIRTrack provide historical tracking and operational context
* Protocol documentation defines auditable accounting flows for vault exits and epoch settlement

![AIRdApp Home](https://4285061132-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1P44hSYTmZyfoGrUcgMT%2Fuploads%2Fgit-blob-4dbe581b46ee4a6264a619547b9e89ff00642f07%2Fairdapp-home.png?alt=media) *Figure: AIRdApp home interface showing the unified entry point for AIR3 modules and community access links.*

*AIRdApp product hub with modular access to AIRTrack, AIRTrading, AIRSocial, AIRSponsor, and AIRTool.*

## AIRTrading Engine at a glance

The AIRTrading Engine uses a single vault model with percentage-based user shares. A withdrawal request closes the same percentage of **all** open positions pro-rata, creates an exit balance, and settles through a fixed 7-day delay via an ExitTicket.

![AIRTrading Engine Diagram](https://4285061132-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1P44hSYTmZyfoGrUcgMT%2Fuploads%2Fgit-blob-aabab94762326b569c4502ccb6feeda92218ab9d%2Fairtrading-engine-diagram.png?alt=media) *Figure: AIRTrading Engine high-level flow showing vault routing, strategy execution, profit splitting, and AIR3 buyback/user reward distribution.*

*High-level AIRTrading Engine architecture showing vault routing, strategy execution, profit splitting, buyback, and user rewards.*

## Where to start

* New readers: [Quickstart](https://airewardrop.gitbook.io/air3/getting-started/quickstart)
* Product overview: [Products Overview](https://airewardrop.gitbook.io/air3/products/overview)
* Protocol logic: [Protocol Overview](https://airewardrop.gitbook.io/air3/protocol/overview)
* Frequently asked questions: [FAQ](https://github.com/AIRewardrop/air3-docs/blob/main/resources/faq.md)
* Official links: [Official Links](https://airewardrop.gitbook.io/air3/resources/official-links)


---

# 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://airewardrop.gitbook.io/air3/readme.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.