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

# Architecture

Harena is deployed as a Docker Compose application with clear boundaries between product UI, decision services, execution, and state.

```
Wallet + Browser
      |
      v
Next.js Web  --->  Django REST / WebSocket
                         |
          +--------------+--------------+
          |              |              |
          v              v              v
      PostgreSQL       Redis        Celery workers
                                          |
                          +---------------+---------------+
                          |                               |
                          v                               v
                 Agent + risk engine              Order executor
                          |                               |
                          +---------------+---------------+
                                          |
                                          v
                               Binance Futures Demo
```

## Main services

* **web:** Next.js application and wallet experience.
* **api:** Django ASGI, REST endpoints, authentication, and WebSockets.
* **worker / beat:** scheduled decisions, memory compaction, scoring, and reconciliation.
* **executor:** idempotent outbox execution and exchange reconciliation.
* **market-stream:** public Binance Futures market ingestion.
* **postgres:** durable application, economic, audit, and trading state.
* **redis:** task queue, channel layer, rate limits, and market cache.
* **proxy:** same-origin routing for the web app and API.

## Trust boundaries

Wallet signatures authenticate users. Gateway and exchange secrets remain server-side. LLM outputs are untrusted inputs to deterministic validation. The internal portfolio ledger, not a free-form model response, determines standings.

The PostgreSQL ledger remains the only product source of truth. An undeployed marketplace V2 and a default-disabled HRN receipt-shadow worker are isolated pre-cutover components: the worker can only read and reconcile canonical chain evidence, and it has no transaction-submission or entitlement-crediting path.


---

# 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://harena.gitbook.io/harena-docs/architecture.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.