> For the complete documentation index, see [llms.txt](https://docs.polygoatbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polygoatbot.com/system-architecture.md).
# System Architecture
PolyGoat operates as a custodial execution system powered by Fireblocks — institutional-grade custody infrastructure used by the world's largest crypto firms. The Execution Engine interfaces directly with the Polymarket API, so trades fire without the user ever leaving the app. No external wallet connection required.
**Signal Engine** ingests real-time CLOB and external price data, computing price velocity, volume acceleration and liquidity imbalance — latency \~12–38ms.
**Execution Engine** prepares, signs and submits orders through the Fireblocks policy engine, optimising for minimal time-to-fill — \~100–300ms end to end.
**RDC Node Layer** routes through QuickNode (shared, 99.99% uptime) and Chainstack (custom, Polygon-native dedicated endpoints) with automatic node selection and failover.
**Risk & Allocation Layer** enforces per-trade sizing, maximum exposure per epoch and trade frequency, preventing overallocation across market conditions.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.polygoatbot.com/system-architecture.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.