> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/risk.md).
# Rules & Limits
Rules & Limits are each firm's hard constraints. TradeSurge checks them before a trade fires, not after.
Rules & Limits are the hard constraints a prop firm puts on an account. One broken rule ends an account, and the more accounts you run, the harder the rule maths is to hold in your head. TradeSurge checks every rule before a trade fires, so you do not have to.
## What each account is held to
| Name | What it means |
| -------------------- | ---------------------------------------------------------------------------------- |
| **Daily drawdown** | The most the account can lose in one firm day. |
| **Maximum drawdown** | The most the account can lose overall, static or trailing depending on the firm. |
| **Profit target** | The target to pass in Evaluation, or your own goal in Funded. |
| **Daily reset** | When the firm's day starts over for the daily drawdown. |
| **Consistency** | The firm's cap on how much of your profit can come from one day, where it has one. |
## Protection comes in layers
TradeSurge protects each account in four layers, from the gentlest to the hardest stop.
* **Risk dial** sizes every trade, so no single trade risks more than you set.
* **Caps** stop an oversized order, and **circuit breakers** (coming soon) will stop new entries after a bad day.
* **Breach Guard** blocks and then flattens an account before it crosses a firm limit.
* **Kill switch** closes every position on every account, on your command.
## Prevent, not alert
Most tools tell you after a limit is broken. TradeSurge is built to stop the trade that would break it. When a firm's rule is unclear, it takes the stricter reading.
## Next steps
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tradesurge.co/platform/risk.md?ask=&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 `automate deployments from our CI pipeline` 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.