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

# The 7 Layer Engine

```
             ARBYDEX
                 │
      INTELLIGENT ARBITRAGE ENGINE
                 │
   ┌─────────────┴─────────────┐
   │                           │
   DISCOVERY 2. LIQUIDITY
│ │
└─────────────┬─────────────┘
│
3. PROFITABILITY
│
4. RISK ANALYSIS
│
5. MEV DEFENSE
│
6. EXECUTION
│
7. LEARNING   
```

#### Layer 1

**Discovery AI**

Identifies potential arbitrage opportunities across supported markets.

#### Layer 2

**Liquidity AI**

Evaluates available liquidity and potential market impact.

#### Layer 3

**Profitability AI**

Evaluates potential execution economics after relevant costs and conditions.

#### Layer 4

**Risk AI**

Evaluates market and execution risks before the opportunity proceeds.

#### Layer 5

**MEV Defense AI**

Analyzes blockchain execution conditions and potential MEV exposure.

#### Layer 6

**Execution AI**

Coordinates qualified opportunities with the execution process.

#### Layer 7

**Learning AI**

Uses historical execution information and system feedback to continuously improve decision processes.

### The Complete ARBYDEX Intelligence Loop

The seven layers operate as a connected system rather than isolated components.

```
        MARKET DATA
             ↓
     ┌───────────────┐
     │  DISCOVERY AI │
     └───────┬───────┘
             ↓
    ┌─────────────────┐
    │  LIQUIDITY AI   │
    └────────┬────────┘
             ↓
   ┌─────────────────────┐
   │ PROFITABILITY AI    │
   └──────────┬──────────┘
              ↓
      ┌───────────────┐
      │    RISK AI    │
      └───────┬───────┘
              ↓
    ┌─────────────────┐
    │  MEV DEFENSE AI │
    └────────┬────────┘
             ↓
    ┌─────────────────┐
    │  EXECUTION AI   │
    └────────┬────────┘
             ↓
       ON CHAIN TX
             ↓
     TRANSACTION DATA
             ↓
      ┌─────────────┐
      │ LEARNING AI │
      └──────┬──────┘
             │
             └──────────────→ CONTINUOUS IMPROVEMENT
```

#### One Engine. Seven Intelligence Layers.

ARBYDEX brings market discovery, liquidity intelligence, profitability analysis, risk evaluation, MEV defense, smart execution, and continuous learning into a unified arbitrage infrastructure.

**Intelligence Before Execution.**

**Discover. Analyze. Validate. Execute. Monitor. Learn.**

Untuk bagian **Technology** ini, saya juga bisa membuat **illustration/diagram profesional untuk “The 7 Layer Engine”** yang langsung cocok dimasukkan ke GitBook ARBYDEX.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://arbydex.gitbook.io/arbydex/arbydex-technology/the-7-layer-engine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.