# Solution Overview

#### What UNIKO delivers

UNIKO coordinates three layers into one operating loop:

1. Participation Layer (Quant Index)\
   Defines entry tiers, lifecycle, and settlement rules.
2. Execution Layer (A.M.M.Q)\
   Runs quant trading, liquidity operations, and execution governance during defined windows.
3. Token and Settlement Layer (PAI, BULX, QUSD)\
   Provides market demand linkage, liquidity pairing, and stable internal settlement.

#### The UNIKO operating loop

UNIKO aims to maintain a continuous cycle:

1\.        Participation enters in structured rounds

2\.        Capital is deployed via execution logic

3\.        Liquidity flows through LP and market routing

4\.        Market demand is reinforced via participation-linked asset requirements

5\.        Positions transfer and the cycle continues

#### High-level ecosystem process flow

flowchart LR\
  U\[User] -->|Enter with PAI or USDT| QI\[UNIKO Quant Index]\
  QI -->|If USDT entry: buy/repurchase PAI| M\[(Open Market)]\
  U -->|If PAI entry: user acquires PAI| M\
  QI -->|Start round| AMMQ\[UNIKO A.M.M.Q Execution]\
  AMMQ -->|Trades & liquidity operations| VEN\[(CEX / DEX Venues)]\
  VEN -->|Fills, slippage, state| AMMQ\
  AMMQ -->|Round outcome computed| QI\
  QI -->|Maturity transfer required| NEXT\[Next Participant]\
  QI -->|Settlement & conversion| QUSD\[QUSD]\
  QUSD -->|Conversion (buffered release)| BULX\[BULX]\
  BULX -->|LP pairing with PAI| LP\[PAI–BULX LP]\
  LP -->|Liquidity depth support| VEN

#### Where PAI comes from (market sourcing logic)

UNIKO’s participation logic is designed so that:

·      Participation with PAI requires acquiring PAI from the market.

·      Participation with USDT triggers system-side market acquisition/repurchase of PAI.

This design aims to link participation volume to market demand rather than relying on arbitrary token issuance.


---

# 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://uniko.gitbook.io/uniko-whitepaper/solution-overview.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.