Trading arena fed by Alpaca data via trtools2. MAF never calls Alpaca directly — trtools2 owns the Alpaca ingestion (live feed engine writes bars/news to Redis Streams; the dashboard's HTTP API serves historical queries from QuestDB). Two routes into the same data: • Hot path — trtools2_bars / trtools2_news Redis Streams. Sub-second latency, populated by the live feed engine. • Warm path — trtools2_api HTTP client. Used when the analyst needs bars over a specific window or wants the per-symbol coverage stats. Bring up requires: trtools2 feed engine running, trtools2 dashboard on :8888. The Setup tab's freshness badges flag whether each route is live.
Configure the arena's metadata, data sources, agents and phases. Changes write to the YAML file. Restart the app to apply.
Edit arena configuration (JSON). Changes write to YAML file — restart to apply.
Data sources bound to this arena. Agents access these via ReAct tool calls.
| Source Name | Adapter | Module | Parameters | Used By |
|---|---|---|---|---|
| bars_1m | trtools2_bars | trtools2 | — | trtools2_analyst |
| bars_1h | trtools2_bars | trtools2 | — | trtools2_analyst |
| news_live | trtools2_news | trtools2 | — | trtools2_analyst |
| strategy_events | trtools2_strategy_events | trtools2 | — | trtools2_analyst |
| history_bars | trtools2_api | trtools2 | — | trtools2_analyst |
| snapshot | trtools2_api | trtools2 | — | trtools2_analyst |
| feed_health | trtools2_api | trtools2 | — | trtools2_analyst |
Decision trail — every arena run is saved for review and auditing.