> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cooket.fun/llms.txt
> Use this file to discover all available pages before exploring further.

# System architecture

> Contracts, browser, indexing, API, database, and realtime data flow.

```mermaid theme={null}
flowchart TB
  W[External EVM wallet] --> B[Cooket browser]
  B -->|reads, simulations, transactions| C[Arc Testnet contracts]
  C -->|confirmed logs over HTTP RPC| I[Go indexer]
  I -->|canonical blocks and projections| P[(PostgreSQL)]
  P --> A[Go API]
  A -->|canonical JSON| B
  P --> R[Realtime market service]
  C -->|unconfirmed logs over WebSocket RPC| R
  R -->|live-only SSE| B
```

The browser is the only user transaction initiator. Contracts enforce supply, curve, fees, graduation, custody, CTO, and rewards behavior. The indexer consumes confirmed logs, detects canonical-chain changes, and writes raw provenance plus derived projections atomically. PostgreSQL is the API's read source and the realtime service's market registry.

The realtime service does not write to PostgreSQL. It watches registered curve and canonical pool addresses and broadcasts provisional market events. Canonical API results eventually replace that overlay.

Redis is configured alongside API/indexer deployments, but the current public API data path documented here is PostgreSQL-backed. Compose supports local and split production-style service layouts; it is configuration evidence, not production-health evidence.